|| ||Matthew Garrett <mjg-AT-redhat.com> |
|| ||Paul Walmsley <paul-AT-pwsan.com> |
|| ||Re: [PATCH 0/8] Suspend block api (version 6) |
|| ||Fri, 14 May 2010 21:32:02 +0100|
|| ||Greg Kroah-Hartman <gregkh-AT-suse.de>,
Jesse Barnes <jbarnes-AT-virtuousgeek.org>, linux-kernel-AT-vger.kernel.org,
Liam Girdwood <lrg-AT-slimlogic.co.uk>, Len Brown <len.brown-AT-intel.com>,
Jacob Pan <jacob.jun.pan-AT-linux.intel.com>,
Oleg Nesterov <oleg-AT-redhat.com>, linux-omap-AT-vger.kernel.org,
Linus Walleij <linus.walleij-AT-stericsson.com>,
Daniel Walker <dwalker-AT-codeaurora.org>,
"Theodore Ts'o" <tytso-AT-mit.edu>, Brian Swetland <swetland-AT-google.com>,
Mark Brown <broonie-AT-opensource.wolfsonmicro.com>,
Geoff Smith <geoffx.smith-AT-intel.com>, Tejun Heo <tj-AT-kernel.org>,
Andrew Morton <akpm-AT-linux-foundation.org>,
Wu Fengguang <fengguang.wu-AT-intel.com>,
Arjan van de Ven <arjan-AT-infradead.org>|
|| ||Article, Thread
On Fri, May 14, 2010 at 02:20:43PM -0600, Paul Walmsley wrote:
> On Mon, 3 May 2010, Matthew Garrett wrote:
> > I agree that the runtime scenario is a far more appealing one from an
> > aesthetic standpoint, but so far we don't have a very compelling
> > argument for dealing with the starting and stopping of userspace.
> The problem of how to start and stop (some) userspace is not specifically
> system power management-related, nor top-down, /sys/power/state-suspend
> related. PM is just one potential user.
> It's hard to see how the Android opportunistic suspend approach would be
> useful for the other use-cases (e.g., checkpoint/restart). On the other
> hand, it's easier to see how something like freezer cgroups could be
> useful for system power management and checkpoint/restart.
And difficult to see how to implement something using freezer cgroups
that actually works in this case. Look, I don't want to sound like I
have a one-track mind or anything, but all of these arguments would be
significantly more compelling if someone would actually provide a
concrete implementation proposal that deals with the set of use-cases
that Google's implementation does and which doesn't make anyone cry.
Otherwise the immeasurably most likely outcome is that this code gets
merged and we get to live with it.
Matthew Garrett | email@example.com
to post comments)