From: Maximilian Heyne <mheyne@amazon.de>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Maximilian Heyne <mheyne@amazon.de>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
<intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v2] drivers, ixgbe: show VF statistics
Date: Fri, 6 May 2022 06:44:40 +0000 [thread overview]
Message-ID: <20220506064440.57940-1-mheyne@amazon.de> (raw)
In-Reply-To: <20220504201632.2a41a3b9@kernel.org>
On 2022-05-04T20:16:32-07:00 Jakub Kicinski <kuba@kernel.org> wrote:
> On Tue, 3 May 2022 15:00:17 +0000 Maximilian Heyne wrote:
> > + for (i = 0; i < adapter->num_vfs; i++) {
> > + ethtool_sprintf(&p, "VF %u Rx Packets", i);
> > + ethtool_sprintf(&p, "VF %u Rx Bytes", i);
> > + ethtool_sprintf(&p, "VF %u Tx Packets", i);
> > + ethtool_sprintf(&p, "VF %u Tx Bytes", i);
> > + ethtool_sprintf(&p, "VF %u MC Packets", i);
> > + }
>
> Please drop the ethtool stats. We've been trying to avoid duplicating
> the same stats in ethtool and iproute2 for a while now.
>
I can see the point that standard metrics should only be reported via the
iproute2 interface. However, in this special case this patch was intended to
converge the out-of-tree driver with the in-tree version. These missing stats
were breaking our userspace. If we now switch solely to iproute2 based
statistics both driver versions would diverge even more. So depending on where a
user gets the ixgbe driver from, they have to work-around.
I can change the patch as requested, but it will contradict the inital
intention. At least Intel should then port this change to the external driver as
well. Let's get a statement from them.
Amazon Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss
Eingetragen am Amtsgericht Charlottenburg unter HRB 149173 B
Sitz: Berlin
Ust-ID: DE 289 237 879
next prev parent reply other threads:[~2022-05-06 6:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-03 15:00 [PATCH net-next v2] drivers, ixgbe: show VF statistics Maximilian Heyne
2022-05-05 3:16 ` Jakub Kicinski
2022-05-06 6:44 ` Maximilian Heyne [this message]
2022-05-06 16:13 ` Jakub Kicinski
2022-05-06 16:20 ` Tony Nguyen
2022-05-09 7:39 ` Maximilian Heyne
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=20220506064440.57940-1-mheyne@amazon.de \
--to=mheyne@amazon.de \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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