mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Tejun Heo <htejun@gmail.com>
Cc: kernel list <linux-kernel@vger.kernel.org>, axboe@suse.de
Subject: Re: SATA powersave patches
Date: Mon, 18 Sep 2006 12:05:48 +0200	[thread overview]
Message-ID: <20060918100548.GJ3746@elf.ucw.cz> (raw)
In-Reply-To: <4505394F.6060806@gmail.com>

Hi!

> >Thanks... I got it to work (on 2 the old tree, I was not able to
> >forward-port it), but power savings were not too big (~0.1W, maybe).
> >
> >I'm getting huge (~1W) savings by powering down SATA controller, as in
> >ahci_pci_device_suspend().
> 
> Yeah, it only turns off SATA PHY, so it doesn't result in huge saving. 
> IIRC, it was somewhere around 5 percent on my notebook w/ static 
> linksave mode (turning PHY off on empty port).  But link powersaving 
> introduces virtually no recognizable delay, so it's nice to have.

Yes, any powersavings without cost are a good idea. 

> Can you check if there is any difference between [D/H]IPS and static? 
> ICH6M on my notebook can't do DIPS/HIPS, so I couldn't compare them 
> against static.

What is D/HIPS? I could not find anything relevant..

> >It would be great to be able to power SATA
> >controller down, then power it back up when it is needed... I tried
> >following hack, but could not get it to work. Any ideas?
> 
> 1. One way to do it would be by dynamic power management.  It would be 
> nice to have wake-up mechanism at the block layer.  Idle timer can run 
> in the block layer or it can be implemented in the userland.
> 
> ATM, this implies that the attached devices are powered down too 
> (spindown).  As spinning up takes quite some time, we can implement 

For now, powering down controller when disks are spinned down would be
very nice first step.

When I forced disk to be spinned down (with power/state file)
controller actually survived power down/power up... unfortunately with
so long delay (~30 sec) that it is not usable in practice.

> 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 :-).
								Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2006-09-18 10:06 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       ` Pavel Machek
2006-09-11 10:24         ` Tejun Heo
2006-09-18 10:05           ` Pavel Machek [this message]
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
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=20060918100548.GJ3746@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=axboe@suse.de \
    --cc=htejun@gmail.com \
    --cc=linux-kernel@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

all inboxes | Powered by JetHome®