public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>, axboe@suse.de
Subject: Re: SATA powersave patches
Date: Tue, 07 Nov 2006 02:44:26 +0900	[thread overview]
Message-ID: <454F747A.9050209@gmail.com> (raw)
In-Reply-To: <20061106135751.GA13517@elf.ucw.cz>

Pavel Machek wrote:
> I'm probably doing something wrong, but...
> 
> I'm on commit 
> 
> commit 9a7b050525f7d70d2ed62affb691b9d4ca2b82d2
> tree b8195e5625dc5bad6757b0dddec0dacf416a0779
> parent 50c3086de212ce56eaa2bf284586fb021615b5e1
> author Tejun Heo <htejun@gmail.com> Mon, 16 Oct 2006 07:24:57 +0900
> committer Tejun Heo <htejun@gmail.com> Mon, 16 Oct 2006 07:24:57 +0900
> 
>     [PATCH] sata_sil24: implement PORT_RST
> 
>     As DEV_RST (hardreset) sometimes fail to recover the controller
>     (especially after PMP DMA CS errata).  In such cases, perform
> PORT_RST
>     prior to DEV_RST.
> 
>     Signed-off-by: Tejun Heo <htejun@gmail.com>
> 
> (2.6.19-rc1)
> 
> and I do not see powersave tunable:
> 
> root@amd:/sys/module# ls libata/parameters/
> ata_probe_timeout         atapi_enabled hotplug_polling_interval
> atapi_dmadir              fua
> 
> ...how do I pull working version?

I haven't updated link powersave patch yet.  Core implementation was 
agreed on but interface hasn't been decided yet.  Maybe it's about time 
to add /sys/class/ata_{host|device}/.  So, the patchset is pushed back 
for the time being.

>>>> So, I think option #1 is the way to go - implementing leveled dynamic 
>>>> power management infrastructure and adding support in the block layer. 
>>>> What do you think?
>>> Would be nice :-).
>> So, do you think we're ready for another PM infrastructure update?  :-P
> 
> Well... things are pretty quiet in that area just now... So yes.

If I understood correctly, the high power consumption of ahci controller 
can be solved by dynamically turning off command processing while the 
controller is idle, which fits nicely into link powersaving, right?  So, 
I think full-fledged leveled dynamic PM would be an overkill for this 
particular problem, but then again, maybe the correct way to implement 
link powersaving is via leveled dynamic PM.  I'll give it more thoughts.

Thanks.

-- 
tejun

  reply	other threads:[~2006-11-06 17:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060908110346.GC920@elf.ucw.cz>
     [not found] ` <45015767.1090002@gmail.com>
     [not found]   ` <20060908123537.GB17640@elf.ucw.cz>
     [not found]     ` <4501655F.5000103@gmail.com>
2006-09-10 22:48       ` SATA powersave patches Pavel Machek
2006-09-11 10:24         ` Tejun Heo
2006-09-18 10:05           ` Pavel Machek
2006-09-18 10:38             ` Tejun Heo
2006-11-06 13:57               ` Pavel Machek
2006-11-06 17:44                 ` Tejun Heo [this message]
2006-11-12 18:39                   ` Pavel Machek
2006-11-21  4:30                     ` Tejun Heo
2006-11-21 23:07                       ` Pavel Machek

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=454F747A.9050209@gmail.com \
    --to=htejun@gmail.com \
    --cc=axboe@suse.de \
    --cc=linux-kernel@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