From: Gal Pressman <galp@mellanox.com>
To: netdev@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
Vidya Sagar Ravipati <vidya@cumulusnetworks.com>,
Saeed Mahameed <saeedm@mellanox.com>
Cc: David Decotigny <decot@googlers.com>,
Ben Hutchings <ben@decadent.org.uk>,
Gal Pressman <galp@mellanox.com>
Subject: [PATCH RFC 0/2] ethtool: Add actual port speed reporting
Date: Wed, 2 Nov 2016 17:35:12 +0200 [thread overview]
Message-ID: <1478100914-23610-1-git-send-email-galp@mellanox.com> (raw)
Sending RFC to get feedback for the following ethtool proposal:
In some cases such as virtual machines and multi functions (SR-IOV), the actual
bandwidth exposed for each machine is not accurately shown in ethtool.
Currently ethtool shows only physical port link speed.
In our case we would like to show the virtual port operational link speed
which in some cases is less than the physical port speed.
This will give users better visibility for the actual speed running on their device.
$ ethtool ens6
...
Speed: 50000Mb/s
Actual speed: 25000Mb/s
Gal Pressman (2):
ethtool: Add get actual port speed support
net/mlx5e: Add support for ethtool get actual speed callback
drivers/net/ethernet/mellanox/mlx5/core/en_ethtool.c | 7 +++++++
include/linux/ethtool.h | 1 +
include/uapi/linux/ethtool.h | 2 ++
net/core/ethtool.c | 20 ++++++++++++++++++++
4 files changed, 30 insertions(+)
--
2.7.4
next reply other threads:[~2016-11-02 15:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-02 15:35 Gal Pressman [this message]
2016-11-02 15:35 ` [PATCH RFC 1/2] ethtool: Add get actual port speed Gal Pressman
2016-11-02 15:35 ` [PATCH RFC 2/2] net/mlx5e: Add support for ethtool get actual speed callback Gal Pressman
2016-11-02 15:50 ` [PATCH RFC 0/2] ethtool: Add actual port speed reporting Mintz, Yuval
2016-11-03 16:59 ` Gal Pressman
2016-11-03 17:09 ` Rick Jones
2016-11-09 9:32 ` Saeed Mahameed
2016-11-03 7:02 ` Or Gerlitz
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=1478100914-23610-1-git-send-email-galp@mellanox.com \
--to=galp@mellanox.com \
--cc=ben@decadent.org.uk \
--cc=decot@googlers.com \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.com \
--cc=vidya@cumulusnetworks.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