[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4C019C75.6020000@crca.org.au>
Date: Sun, 30 May 2010 09:00:05 +1000
From: Nigel Cunningham <ncunningham@...a.org.au>
To: Arve Hjønnevåg <arve@...roid.com>
CC: Alan Stern <stern@...land.harvard.edu>,
Peter Zijlstra <peterz@...radead.org>,
Brian Swetland <swetland@...gle.com>,
Ingo Molnar <mingo@...e.hu>,
LKML <linux-kernel@...r.kernel.org>,
Florian Mickler <florian@...kler.org>,
Linux PM <linux-pm@...ts.linux-foundation.org>,
Thomas Gleixner <tglx@...utronix.de>,
Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [linux-pm] [PATCH 0/8] Suspend block api (version 8)
Hi.
I like the sound of this much better too, but...
On 30/05/10 08:13, Arve Hjønnevåg wrote:
> On Sat, May 29, 2010 at 7:10 AM, Alan Stern<stern@...land.harvard.edu> wrote:
>> There is no /sys/power/policy file. In place of opportunistic suspend,
>> we have "QoS-based suspend". This is initiated by userspace writing
>> "qos" to /sys/power/state, and it is very much like suspend-to-RAM.
>
> Why do you want to tie it to a specific state?
I do agree here. I would suggest that all /sys/power/state possibilities
should have a qos- equivalent. You might not want to use any or all of
them, but they should be available.
Regards,
Nigel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists