Netdev List
 help / color / mirror / Atom feed
From: Gal Pressman <galp.dev@gmail.com>
To: "Mintz, Yuval" <Yuval.Mintz@cavium.com>,
	Gal Pressman <galp@mellanox.com>,
	"netdev@vger.kernel.org" <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>
Subject: Re: [PATCH RFC 0/2] ethtool: Add actual port speed reporting
Date: Thu, 3 Nov 2016 18:59:11 +0200	[thread overview]
Message-ID: <7a681afa-a5fa-3039-873c-d13617484cc9@gmail.com> (raw)
In-Reply-To: <BL2PR07MB23069B0DB17B981AA43775B18DA00@BL2PR07MB2306.namprd07.prod.outlook.com>



On 02/11/2016 17:50, Mintz, Yuval wrote:
>> 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
> 
> Not saying this is a bad thing, but where exactly is it listed that ethtool has
> to show the physical port speed?
> E.g., bnx2x shows the logical speed instead, and has been doing that for years.
> [Perhaps that's a past wrongness, but that's how it goes].
> 
> And besides, one can argue that in the SR-IOV scenario the VF has no business
> knowing the physical port speed.
> 

Good point, but there are more use-cases we should consider.
For example, when using Multi-Host/Flex-10/Multi-PF each PF should
be able to query both physical port speed and actual speed.

  reply	other threads:[~2016-11-03 16:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-02 15:35 [PATCH RFC 0/2] ethtool: Add actual port speed reporting Gal Pressman
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 [this message]
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=7a681afa-a5fa-3039-873c-d13617484cc9@gmail.com \
    --to=galp.dev@gmail.com \
    --cc=Yuval.Mintz@cavium.com \
    --cc=ben@decadent.org.uk \
    --cc=decot@googlers.com \
    --cc=galp@mellanox.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