From: Simon Horman <horms@kernel.org>
To: Kohei Enju <enjuk@amazon.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
kohei.enju@gmail.com, Paul Menzel <pmenzel@molgen.mpg.de>
Subject: Re: [Intel-wired-lan] [PATCH v2 iwl-next 1/2] igbvf: add lbtx_packets and lbtx_bytes to ethtool statistics
Date: Wed, 27 Aug 2025 13:27:12 +0100 [thread overview]
Message-ID: <20250827122712.GA1063@horms.kernel.org> (raw)
In-Reply-To: <20250818151902.64979-5-enjuk@amazon.com>
On Tue, Aug 19, 2025 at 12:18:26AM +0900, Kohei Enju wrote:
> Currently ethtool shows lbrx_packets and lbrx_bytes (Good RX
> Packets/Octets loopback Count), but doesn't show the TX-side equivalents
> (lbtx_packets and lbtx_bytes). Add visibility of those missing
> statistics by adding them to ethtool statistics.
>
> In addition, the order of lbrx_bytes and lbrx_packets is not consistent
> with non-loopback statistics (rx_packets, rx_bytes). Therefore,
> align the order by swapping positions of lbrx_bytes and lbrx_packets.
>
> Tested on Intel Corporation I350 Gigabit Network Connection.
>
> Before:
> # ethtool -S ens5 | grep -E "x_(bytes|packets)"
> rx_packets: 135
> tx_packets: 106
> rx_bytes: 16010
> tx_bytes: 12451
> lbrx_bytes: 1148
> lbrx_packets: 12
>
> After:
> # ethtool -S ens5 | grep -E "x_(bytes|packets)"
> rx_packets: 748
> tx_packets: 304
> rx_bytes: 81513
> tx_bytes: 33698
> lbrx_packets: 97
> lbtx_packets: 109
> lbrx_bytes: 12090
> lbtx_bytes: 12401
>
> Reviewed-by: Paul Menzel <pmenzel@molgen.mpg.de>
> Signed-off-by: Kohei Enju <enjuk@amazon.com>
Reviewed-by: Simon Horman <horms@kernel.org>
WARNING: multiple messages have this Message-ID (diff)
From: Simon Horman <horms@kernel.org>
To: Kohei Enju <enjuk@amazon.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Przemek Kitszel <przemyslaw.kitszel@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
kohei.enju@gmail.com, Paul Menzel <pmenzel@molgen.mpg.de>
Subject: Re: [PATCH v2 iwl-next 1/2] igbvf: add lbtx_packets and lbtx_bytes to ethtool statistics
Date: Wed, 27 Aug 2025 13:27:12 +0100 [thread overview]
Message-ID: <20250827122712.GA1063@horms.kernel.org> (raw)
In-Reply-To: <20250818151902.64979-5-enjuk@amazon.com>
On Tue, Aug 19, 2025 at 12:18:26AM +0900, Kohei Enju wrote:
> Currently ethtool shows lbrx_packets and lbrx_bytes (Good RX
> Packets/Octets loopback Count), but doesn't show the TX-side equivalents
> (lbtx_packets and lbtx_bytes). Add visibility of those missing
> statistics by adding them to ethtool statistics.
>
> In addition, the order of lbrx_bytes and lbrx_packets is not consistent
> with non-loopback statistics (rx_packets, rx_bytes). Therefore,
> align the order by swapping positions of lbrx_bytes and lbrx_packets.
>
> Tested on Intel Corporation I350 Gigabit Network Connection.
>
> Before:
> # ethtool -S ens5 | grep -E "x_(bytes|packets)"
> rx_packets: 135
> tx_packets: 106
> rx_bytes: 16010
> tx_bytes: 12451
> lbrx_bytes: 1148
> lbrx_packets: 12
>
> After:
> # ethtool -S ens5 | grep -E "x_(bytes|packets)"
> rx_packets: 748
> tx_packets: 304
> rx_bytes: 81513
> tx_bytes: 33698
> lbrx_packets: 97
> lbtx_packets: 109
> lbrx_bytes: 12090
> lbtx_bytes: 12401
>
> Reviewed-by: Paul Menzel <pmenzel@molgen.mpg.de>
> Signed-off-by: Kohei Enju <enjuk@amazon.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2025-08-27 12:27 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 15:18 [Intel-wired-lan] [PATCH v2 iwl-next 0/2] igbvf: ethtool statistics improvements Kohei Enju
2025-08-18 15:18 ` Kohei Enju
2025-08-18 15:18 ` [Intel-wired-lan] [PATCH v2 iwl-next 1/2] igbvf: add lbtx_packets and lbtx_bytes to ethtool statistics Kohei Enju
2025-08-18 15:18 ` Kohei Enju
2025-08-19 8:17 ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-08-19 8:17 ` Loktionov, Aleksandr
2025-08-27 12:27 ` Simon Horman [this message]
2025-08-27 12:27 ` Simon Horman
2025-08-28 10:12 ` [Intel-wired-lan] " Romanowski, Rafal
2025-08-28 10:12 ` Romanowski, Rafal
2025-08-18 15:18 ` [Intel-wired-lan] [PATCH v2 iwl-next 2/2] igbvf: remove redundant counter rx_long_byte_count from " Kohei Enju
2025-08-18 15:18 ` Kohei Enju
2025-08-19 8:19 ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-08-19 8:19 ` Loktionov, Aleksandr
2025-08-27 13:49 ` Simon Horman
2025-08-27 13:49 ` Simon Horman
2025-09-16 9:22 ` [Intel-wired-lan] [PATCH v2 iwl-next 0/2] igbvf: ethtool statistics improvements Romanowski, Rafal
2025-09-16 9:22 ` Romanowski, Rafal
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=20250827122712.GA1063@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=enjuk@amazon.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kohei.enju@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pmenzel@molgen.mpg.de \
--cc=przemyslaw.kitszel@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.