lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 30 May 2010 09:00:05 +1000
From:	Nigel Cunningham <>
To:	Arve Hjønnevåg <>
CC:	Alan Stern <>,
	Peter Zijlstra <>,
	Brian Swetland <>,
	Ingo Molnar <>,
	LKML <>,
	Florian Mickler <>,
	Linux PM <>,
	Thomas Gleixner <>,
	Alan Cox <>
Subject: Re: [linux-pm] [PATCH 0/8] Suspend block api (version 8)


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<>  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.



To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists