public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Pavel Machek <pavel@suse.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>, axboe@suse.de
Subject: Re: SATA powersave patches
Date: Tue, 21 Nov 2006 13:30:54 +0900	[thread overview]
Message-ID: <456280FE.70607@gmail.com> (raw)
In-Reply-To: <20061112183927.GB5081@ucw.cz>

Hello,

Pavel Machek wrote:
>> 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 
> 
> It is single bit, and it should not even need a timeout, AFAICT, so
> perhaps we should just fix it (no need for dynamic PM layers). It
> probably does not even need to be configurable...

I think this has been discussed in linux-ide recently but just to add my 
2 cents.  ALPE and ASP can cause quite some problems.  Many devices 
don't implement link powermanagement mode properly and some locks up 
completely (recent LG dvd-rams, only physical power removal/reapply can 
recover it) while others (wd raptors) spin down on slumber.  If you turn 
on ALPE and ASP on such devices, all hell will break loose.

Even for devices which implement partial and slumber modes properly, I'm 
not very comfortable with ALPE.  It puts the link into power save mode 
as soon as there is no command pending.  IMHO, that's way too 
aggressive.  It's not like being that aggressive will bring any 
noticeable difference in power consumption.  Disk idle period is too 
long for that level of aggressiveness to be effective.

Thanks.

-- 
tejun

  reply	other threads:[~2006-11-21  4:31 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
2006-11-12 18:39                   ` Pavel Machek
2006-11-21  4:30                     ` Tejun Heo [this message]
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=456280FE.70607@gmail.com \
    --to=htejun@gmail.com \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.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