From: "Kok, Auke" <auke-jan.h.kok@intel.com>
To: Shaohua Li <shaohua.li@intel.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
linux-pci <linux-pci@atrey.karlin.mff.cuni.cz>,
Greg KH <greg@kroah.com>,
"Pallipadi, Venkatesh" <venkatesh.pallipadi@intel.com>
Subject: Re: [RFC] PCIE ASPM support
Date: Mon, 07 Jan 2008 10:19:07 -0800 [thread overview]
Message-ID: <47826D1B.8020301@intel.com> (raw)
In-Reply-To: <1199410324.3631.7.camel@sli10-desk.sh.intel.com>
Shaohua Li wrote:
> On Thu, 2008-01-03 at 11:33 -0800, Kok, Auke wrote:
>> Shaohua Li wrote:
>>> PCI Express ASPM defines a protocol for PCI Express components in the D0
>>> state to reduce Link power by placing their Links into a low power state
>>> and instructing the other end of the Link to do likewise. This
>>> capability allows hardware-autonomous, dynamic Link power reduction
>>> beyond what is achievable by software-only controlled power management.
>>> However, The device should be configured by software appropriately.
>>> Enabling ASPM will save power, but will introduce device latency.
>>>
>>> This patch adds ASPM support in Linux. It introduces a global policy for
>>> ASPM, a sysfs file /sys/module/pcie_aspm/parameters/policy can control
>>> it. The interface can be used as a boot option too. Currently we have
>>> below setting:
>>> -default, BIOS default setting
>>> -powersave, highest power saving mode, enable all available ASPM state
>>> and clock power management
>>> -performance, highest performance, disable ASPM and clock power
>>> management
>>> By default, the 'default' policy is used currently.
>>>
>>> In my test, power difference between powersave mode and performance mode
>>> is about 1.3w in a system with 3 PCIE links.
>>>
>>> please review, any comments will be appreciated.
>>
>> quickly glanced this over since I recently disabled l1 ASPM for the e1000/e1000e
>> driven 82573 device which has issues with l1 ASPM. that immediately gives me the
>> question: how can I continue to disable 1l aspm by default for this device using
>> this infrastructure?
> I used to have a per-device interface, but thought the interface might
> be hard to use for users. If we really need the per-device interface, I
> can re-add it.
>
>> I do like the fact that there is a generic way to re-enable it for the users who
>> want to use it. Can this change be done when the device is already active?
> Yes, at least in my test.
>
>> Can you
>> change this parameter per device/module?
> Another way is to provide a helper for driver, and driver disables
> specific ASPM states. It sounds better to let driver do the disabling,
> as users haven't the knowledge?
agreed, however this could still be usefull in debugging equipment for the
experienced user. In any case an easy handle for the driver to dis/enable ASPM
would certainly help our case, and possibly others.
Auke
next prev parent reply other threads:[~2008-01-07 18:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-03 6:15 [RFC] PCIE ASPM support Shaohua Li
2008-01-03 19:33 ` Kok, Auke
2008-01-04 1:32 ` Shaohua Li
2008-01-07 18:19 ` Kok, Auke [this message]
2008-01-08 1:34 ` Shaohua Li
2008-01-07 22:02 ` Michael Ellerman
2008-01-08 1:35 ` Shaohua Li
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=47826D1B.8020301@intel.com \
--to=auke-jan.h.kok@intel.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=shaohua.li@intel.com \
--cc=venkatesh.pallipadi@intel.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