From: Jeff Garzik <jeff@garzik.org>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Tejun Heo <htejun@gmail.com>,
Kristen Carlson Accardi <kristen.c.accardi@intel.com>,
james.bottomley@steeleye.com, linux-ide@vger.kernel.org,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 0/3] AHCI Link Power Management
Date: Mon, 11 Jun 2007 23:12:48 -0400 [thread overview]
Message-ID: <466E0F30.3000700@garzik.org> (raw)
In-Reply-To: <466E0642.5020506@linux.intel.com>
Arjan van de Ven wrote:
> Tejun Heo wrote:
>> Kristen Carlson Accardi wrote:
>>> Hi,
>>> This series of patches enables Aggressive Link Power Management for
>>> AHCI devices, as documented in the AHCI spec. On my laptop (a Lenovo
>>> X60), this
>>> saves me a full watt of power. On other systems, reported power savings
>>> range from .5-1.5 Watts. It has been tested by the kind folks at
>>> #powertop
>>> with similar results. Please give it a try and let me know what you
>>> think.
>>
>> I'm not sure about this. We need better PM framework to support
>> powersaving in other controllers and some ahcis don't save much when
>> only link power management is used,
>
> do you have data to support this? The data we have from this patch is
> that it saves typically a Watt of power (depends on the machine of
> course, but the range is 0.5W to 1.5W). If you want to also have an even
> more agressive thing where you want to start disabling the entire
> controller... I don't see how this is in conflict with saving power on
> the link level by "just" enabling a hardware feature ....
SATA standard defines lower power phy states. So the same argument
you're using for AHCI applies there too -- "just" enabling an existing
hardware feature.
Jeff
next prev parent reply other threads:[~2007-06-12 3:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-11 18:46 [patch 0/3] AHCI Link Power Management Kristen Carlson Accardi
2007-06-12 1:58 ` Tejun Heo
2007-06-12 2:33 ` Jeff Garzik
2007-06-12 2:34 ` Arjan van de Ven
2007-06-12 3:12 ` Jeff Garzik [this message]
2007-06-12 3:12 ` Arjan van de Ven
2007-06-12 3:18 ` Jeff Garzik
2007-06-12 4:13 ` Tejun Heo
2007-06-12 4:19 ` Arjan van de Ven
2007-06-12 4:40 ` Tejun Heo
2007-06-12 15:56 ` Kristen Carlson Accardi
2007-06-12 4:43 ` Jeff Garzik
2007-06-12 15:43 ` Kristen Carlson Accardi
2007-06-13 14:51 ` Pavel Machek
2007-06-13 9:04 ` Pavel Machek
2007-06-13 16:26 ` Kristen Carlson Accardi
2007-06-14 7:56 ` Tejun Heo
2007-06-13 14:56 ` Pavel Machek
2007-06-14 11:56 ` Jens Axboe
2007-06-14 12:30 ` Tejun Heo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=466E0F30.3000700@garzik.org \
--to=jeff@garzik.org \
--cc=arjan@linux.intel.com \
--cc=htejun@gmail.com \
--cc=james.bottomley@steeleye.com \
--cc=kristen.c.accardi@intel.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).