From: Tejun Heo <tj@kernel.org>
To: Matthew Garrett <mjg59@coreos.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] libata: Add an additional LPM policy to match Intel recommendations
Date: Mon, 13 Apr 2015 10:32:25 -0400 [thread overview]
Message-ID: <20150413143225.GB2596@htj.duckdns.org> (raw)
In-Reply-To: <1428696929-2988-1-git-send-email-mjg59@coreos.com>
On Fri, Apr 10, 2015 at 01:15:29PM -0700, Matthew Garrett wrote:
> Intel publish a document on designing energy efficient SATA devices at
> http://www.intel.com/content/dam/doc/reference-guide/sata-devices-implementation-recommendations.pdf
> which recommends that ALPE be set, ASPE be cleared and that DIPM be enabled
> on the device. Right now we have no policy that matches that - medium_power
> does not enable DIPM and min_power sets ASPE. Add a new low_power policy to
> implement these recommendations. I've left devslp disabled because I'm not
> yet sure what Intel do in that case. With luck this will provide reasonable
> power savings without causing the device breakages we occasionally see with
> the min_power policy.
I suspect the aggressive methods actually don't buy us much, except
for the obsessive mode switchings, in terms of power saving compared
to something more reasonable provided via DIPM and I'm not sure it's a
good idea to introduce yet another mode. I'd be all in for converting
min_power mode to DIPM for cases where we know this actually works
rather than introducing yet another mode. Or if there's a clear power
consumption disadvantage to DIPM, let's conver medium_power to that.
Thanks.
--
tejun
next prev parent reply other threads:[~2015-04-13 14:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 20:15 Matthew Garrett
2015-04-13 14:32 ` Tejun Heo [this message]
2015-04-13 17:52 ` Matthew Garrett
2015-04-13 17:56 ` 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=20150413143225.GB2596@htj.duckdns.org \
--to=tj@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg59@coreos.com \
/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®