On Fri, May 28, 2010 at 07:29:27AM -0700, Brian Swetland wrote: > I need to think more about the cgroups approach, but I'm pretty sure > it still suffers from wakeup race situations, and due to the > complexity of userspace (at least ours), I suspect it would risk > livelock/deadlock/priority-inversion style issues due to interaction > between different processes in different groups. I think the cgroups approach works if you assume that applications that consume wakeup events can be trusted to otherwise be good citizens. Everything that has no direct interest in wakeup events (except the generic Android userspace) can be frozen, and you can use the scheduler to make everything else Just Work. That's a rather big if, but you've got a better idea of the state of the Android app base than I do. -- Matthew Garrett | mjg59@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
