From: Ben Greear <greearb@candelatech.com>
To: Brice Goglin <Brice.Goglin@inria.fr>
Cc: 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:44:39 -0800 [thread overview]
Message-ID: <50BFEA77.5060305@candelatech.com> (raw)
In-Reply-To: <50BFE4D2.90707@inria.fr>
On 12/05/2012 04:20 PM, Brice Goglin wrote:
> Le 05/12/2012 16:01, David Miller a écrit :
>> lspci might be a good place to figure this out :-) It's probably
>> grovelling around in PCI config space to determine these things.
>
> Right, it looks from PCI_EXP_LNKSTA in the config space (only works as
> root). Here's how we do the same in hwloc (using the pciutils lib
> underneath):
>
> https://svn.open-mpi.org/trac/hwloc/browser/trunk/src/topology-libpci.c#L399
Thanks..but it seems easier to just parse the text output of lspci -vvv
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
next prev parent reply other threads:[~2012-12-06 0:44 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
2012-12-06 0:20 ` Brice Goglin
2012-12-06 0:44 ` Ben Greear [this message]
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=50BFEA77.5060305@candelatech.com \
--to=greearb@candelatech.com \
--cc=Brice.Goglin@inria.fr \
--cc=e1000-devel@lists.sourceforge.net \
--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