From: Tejun Heo <htejun@gmail.com>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: Arjan van de Ven <arjan@linux.intel.com>,
Kristen Carlson Accardi <kristen.c.accardi@intel.com>,
jeff@garzik.org, james.bottomley@steeleye.com,
linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org,
linux-kernel@vger.kernel.org, Pavel Machek <pavel@ucw.cz>
Subject: Re: [patch 0/3] AHCI Link Power Management
Date: Thu, 14 Jun 2007 21:30:41 +0900 [thread overview]
Message-ID: <467134F1.1010009@gmail.com> (raw)
In-Reply-To: <20070614115600.GF6149@kernel.dk>
Jens Axboe wrote:
>> 1. It didn't have proper interface with userland. This was mainly
>> because of missing ATA sysfs nodes. I'm not sure whether adding this to
>> scsi node is a good idea.
>>
>> 2. It was focused on SATA link PS and couldn't cover the Lenovo case.
>>
>> I think we need something at the block layer.
>
> I think the hardware method is preferable, actually. Doing this in the
> block layer would mean keeping track of idle time, and that quickly
> turns into a lot of timer management. Not exactly free, in terms of CPU
> usage.
Yeah, software implementation certainly has complexity overhead.
> I've yet to do some power measurements with this ahci patch, I just
> noticed that with min_power performance drops from ~55mb/sec to
> ~15mb/sec sequential on my drive. That's pretty drastic :-)
That's another thing I don't like about ALPE/ASP. According to the
spec, there is no idle timer whatsoever. The controller is supposed to
drive the link into PS mode whenever FIS is not in flight, so the link
goes in and out of PS state repeatedly when commands are issued
back-to-back. Getting out of PS state takes a bit of time and slows
down things.
--
tejun
prev parent reply other threads:[~2007-06-14 12:30 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
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 [this message]
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=467134F1.1010009@gmail.com \
--to=htejun@gmail.com \
--cc=arjan@linux.intel.com \
--cc=james.bottomley@steeleye.com \
--cc=jeff@garzik.org \
--cc=jens.axboe@oracle.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 \
--cc=pavel@ucw.cz \
/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).