On Mon, 2010-05-17 at 22:24 +0100, Matthew Garrett wrote: > On Mon, May 17, 2010 at 11:16:52PM +0200, Linus WALLEIJ wrote: > > Maybe I'm misunderstanding something basic here, but when you say frozen, > > are you referring to freezer control groups > > Documentation/cgroups/freezer-subsystem.txt? > > > > I was more thinking about something new, that isn't freezing anything. > > The only purpose would be to group the stuff that CPUidle can ignore, > > and let CPUidle ignore it, so that the system can still be idled. > > So they'd be on the runqeue but wouldn't factor into cpuidle's > calculations of when the next wakeup should be? Ok. I think that still > leaves you with the same problem - you're not scheduling that task, so > how do you know to execute it when a network packet is received? I think > you also still have the race condition. Couldn't you special case the network packet situation ? Like the idle loop could take into account that there are packets flowing through the networking stack that may need to get handled. Daniel _______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
