From: David Miller <davem@davemloft.net>
To: greearb@candelatech.com
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 17:36:50 -0500 (EST) [thread overview]
Message-ID: <20121205.173650.1310171220758794440.davem@davemloft.net> (raw)
In-Reply-To: <50BFBE05.7020408@candelatech.com>
From: Ben Greear <greearb@candelatech.com>
Date: Wed, 05 Dec 2012 13:35:01 -0800
> It seems the only way to get the current pci-e bus speed & width
> in ixgbe (and probably many other NICs) is by parsing output
> of lspci -vvv.
>
> I'd personally find it easier if this info were available via
> ethtool API.
You could just as easily have ethtool determine the PCI device
location (using existing facilities) and fetch the PCI-e info from the
PCI sysfs files.
There is no reason to extend ethtool for this.
next prev parent reply other threads:[~2012-12-05 22:36 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 [this message]
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
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=20121205.173650.1310171220758794440.davem@davemloft.net \
--to=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