From: Valdis.Kletnieks@vt.edu
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>,
"Kok, Auke" <auke-jan.h.kok@intel.com>
Subject: Re: [PATCH]PCIE ASPM support - takes 2
Date: Wed, 16 Jan 2008 04:31:08 -0500 [thread overview]
Message-ID: <7566.1200475868@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Wed, 16 Jan 2008 13:26:14 +0800." <1200461174.26885.4.camel@sli10-desk.sh.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1401 bytes --]
On Wed, 16 Jan 2008 13:26:14 +0800, Shaohua Li said:
> On Tue, 2008-01-15 at 22:56 -0500, Valdis.Kletnieks@vt.edu wrote:
> > Do you have any numbers on what the added latency is for powersave mode, and
> > a rough idea of how quickly chipsets will drop to low-power? It may affect
> > usability a lot if it's "adds 10ms latency after 100ms idle" or "adds 100ms
> > latency after 5 seconds idle" or some other pattern...
> >
> > (The chipset in my laptop claims to be an 82801G with 4 PCI-Express ports on
> > it - I'm trying to get a rough idea what usage I'd get out of that feature..)
> No, I thought to get the latency impact with ASPM enabled, but haven't
> found a way to measure it. This is why the default setting of ASPM
> currently is using BIOS setting.
It's OK - I spent some time staring at the output of 'lspci -t' on this laptop,
and convinced myself that the numbers won't matter that much - of the 4 PCIE
ports alledged to be there, 2 aren't connected to anything, and the other 2 are
network (a tg3 and an intel 3945) - and those two are both either (depending
where I am) "essentially idle and will almost certainly sleep" or "busy enough
they likely won't sleep no matter *what* the numbers are".
(That's assuming the chipset in question even *does* ASPM - but it wouldn't be
the first time I've tested stuff just to make sure it didn't enable an impossible
hardware option.. ;)
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2008-01-16 9:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-15 5:02 [PATCH]PCIE ASPM support - takes 2 Shaohua Li
2008-01-16 3:56 ` Valdis.Kletnieks
2008-01-16 5:26 ` Shaohua Li
2008-01-16 9:31 ` Valdis.Kletnieks [this message]
[not found] <1200367276.20538.1.camel@sli10-desk.sh.intel.com>
[not found] ` <20080115041943.GS18741@parisc-linux.org>
2008-01-15 5:07 ` Shaohua Li
2008-01-15 12:22 ` Matthew Wilcox
2008-01-16 1:14 ` 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=7566.1200475868@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=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