lists.openwall.net   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  linux-cve-announce  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:	Thu, 10 Nov 2011 07:37:07 -0800
From:	Tejun Heo <tj@...nel.org>
To:	Alan Stern <stern@...land.harvard.edu>
Cc:	Lin Ming <ming.m.lin@...el.com>, linux-kernel@...r.kernel.org,
	linux-ide@...r.kernel.org, linux-scsi@...r.kernel.org,
	linux-pm@...r.kernel.org, Jeff Garzik <jgarzik@...ox.com>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	James Bottomley <JBottomley@...allels.com>,
	Huang Ying <ying.huang@...el.com>,
	Zhang Rui <rui.zhang@...el.com>
Subject: Re: [PATCH v2 0/4] ata port runtime power management support

On Thu, Nov 10, 2011 at 10:30:53AM -0500, Alan Stern wrote:
> Currently, disks will not be runtime-suspended unless (1) the user 
> requests it by setting the appropriate power/control attribute, and (2) 
> the device file is closed (in particular, the disk has no mounted 
> filesystems or swap partitions).  I don't imagine this combination of 
> events is very common for disks using libata.

Empty ports are pretty common and pm should be able to put the
unoccupied ports and the containing pci device into sleep state which
can save some power.  Would be nice to have some numbers tho.  But
either way, if this doesn't break anything, I don't see any reason to
object to it - the hierarchy reorg is more of logical cleanup and
runtime pm is trivial afterwards.

Thanks.

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ