Re: Attempted summary of suspend-blockers LKML thread
Date: Wed Aug 04 2010 - 14:33:02 EST
On Wed, 4 Aug 2010, Matthew Garrett wrote:
On Wed, Aug 04, 2010 at 09:32:16AM -0700, Paul E. McKenney wrote:
If this doesn't work for the Android folks for whatever reason, another
approach would be to do the freeze in user code, which could track
whether any user-level resources (pthread mutexes, SysV semas, whatever)
where held, and do the freeze on a thread-by-thread basis within each
"victim" application as the threads reach safe points.
The main problem I see with the cgroups solution is that it doesn't seem
to do anything to handle avoiding loss of wakeup events.
there are two cgroup solutions in discussion at this point.
weeks ago there was the suggestion to put non-privilaged tasks in a cgroup
so that they could be frozen as a group. I thought the problem there was
that there can be user-space dpendancies that would prevent privilaged
tasks from working.
a couple days ago I made the suggestion to put non-privilaged tasks in a
cgroup so that the idle/suspend decision code could ignore acitivity
caused by this cgroup.
in the second version wakeup events would be 'activity' that would be
counted and therefor the system would not be idle. As for the race with
suspending and new things happening, wouldn't that be handled the same way
that it is in a normal linux box?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/