Re: [PATCH 0/8] Suspend block api (version 6)

[Matthew Garrett <mjg@redhat.com>]

On Fri, May 21, 2010 at 10:51:58AM -0600, Paul Walmsley wrote:

>       B. To prevent untrusted processes from hogging CPUs, the
>          processes can be run in a cgroup that puts all threads in
>          TASK_RUNNING processes into TASK_INTERRUPTIBLE state and
>          calls schedule() [6], upon receipt of some trigger.  This
>          should allow processes to be awakened by an external system
>          event, e.g., network packet received.  When the system
>          returns from the system low-power state and some trigger
>          event happens, those process threads can be placed back into
>          TASK_RUNNING state and rescheduled.

I don't think that works. If I have an app that would generally complete 
some work and then call select(), you'll instead stop it in the middle 
of that work. If that app is the one that should process the wakeup 
event then it'll never be delivered because you've never got back to 
select().

-- 
Matthew Garrett | mjg59@srcf.ucam.org