From: Rick Jones <rick.jones2@hp.com>
To: David Miller <davem@davemloft.net>
Cc: greearb@candelatech.com, netdev@vger.kernel.org,
e1000-devel@lists.sourceforge.net
Subject: Re: Should we report bus width/speed via ethtool?
Date: Wed, 05 Dec 2012 16:08:14 -0800 [thread overview]
Message-ID: <50BFE1EE.6080902@hp.com> (raw)
In-Reply-To: <20121205.190121.1400827550469329286.davem@davemloft.net>
On 12/05/2012 04:01 PM, David Miller wrote:
> lspci might be a good place to figure this out :-) It's probably
> grovelling around in PCI config space to determine these things.
And if not lspci, "pcitop" used to grub around for such things, though
its source may be rather moldy. I'm sure though that if various chipset
providers were willing to document their PCI performance counters,
*someone* would be happy to bring pcitop into the present day...
happy benchmarking,
rick jones
next prev parent reply other threads:[~2012-12-06 0:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 21:35 Should we report bus width/speed via ethtool? Ben Greear
2012-12-05 22:36 ` David Miller
2012-12-05 23:09 ` Ben Greear
2012-12-06 0:01 ` David Miller
2012-12-06 0:08 ` Rick Jones [this message]
2012-12-06 0:20 ` Brice Goglin
2012-12-06 0:44 ` Ben Greear
2012-12-06 2:06 ` Ben Hutchings
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=50BFE1EE.6080902@hp.com \
--to=rick.jones2@hp.com \
--cc=davem@davemloft.net \
--cc=e1000-devel@lists.sourceforge.net \
--cc=greearb@candelatech.com \
--cc=netdev@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