From: Tejun Heo <tj@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] ahci: Allow setting a default LPM policy for mobile chipsets
Date: Mon, 11 Dec 2017 08:54:04 -0800 [thread overview]
Message-ID: <20171211165404.GM2421075@devbig577.frc2.facebook.com> (raw)
In-Reply-To: <20171211165216.5604-1-hdegoede@redhat.com>
On Mon, Dec 11, 2017 at 05:52:16PM +0100, Hans de Goede wrote:
> On many laptops setting a different LPM policy then unknown /
> max_performance can lead to power-savings of 1.0 - 1.5 Watts (when idle).
>
> Modern ultrabooks idle around 6W (at 50% screen brightness), 1.0 - 1.5W
> is a significant chunk of this.
>
> There are some performance / latency costs to enabling LPM by default,
> so it is desirable to make it possible to set a different LPM policy
> for mobile / laptop variants of chipsets / "South Bridges" vs their
> desktop / server counterparts. Also enabling LPM by default is not
> entirely without risk of regressions. At least min_power is known to
> cause issues with some disks, including some reports of data corruption.
>
> This commits adds a new ahci.mobile_lpm_policy kernel cmdline option,
> which defaults to a new SATA_MOBILE_LPM_POLICY Kconfig option so that
> Linux distributions can choose to set a LPM policy for mobile chipsets
> by default.
>
> The reason to have both a kernel cmdline option and a Kconfig default
> value for it, is to allow easy overriding of the default to allow
> trouble-shooting without needing to rebuild the kernel.
>
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Applied to libata/for-4.16.
Thanks, Hans.
--
tejun
prev parent reply other threads:[~2017-12-11 16:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 16:52 [PATCH v2] ahci: Allow setting a default LPM policy for mobile chipsets Hans de Goede
2017-12-11 16:54 ` 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=20171211165404.GM2421075@devbig577.frc2.facebook.com \
--to=tj@kernel.org \
--cc=hdegoede@redhat.com \
--cc=linux-ide@vger.kernel.org \
--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