From: Kohei Enju <enjuk@amazon.com>
To: <intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: 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>,
Kohei Enju <enjuk@amazon.com>
Subject: [PATCH v2 iwl-next 0/2] igbvf: ethtool statistics improvements
Date: Tue, 19 Aug 2025 00:18:25 +0900 [thread overview]
Message-ID: <20250818151902.64979-4-enjuk@amazon.com> (raw)
This series contains:
1. Add missing lbtx_packets and lbtx_bytes counters that are available
in hardware but not exposed via ethtool
2. Remove rx_long_byte_count counter that shows the same value as
rx_bytes
Tested on Intel Corporation I350 Gigabit Network Connection.
Changes:
v1: https://lore.kernel.org/intel-wired-lan/20250813075206.70114-1-enjuk@amazon.com/
v2:
- Remove Tested-by: tag
- Add Reviewed-by: tag
- s/duplicated/redundant/ in commit message of the 2/2 patch
Kohei Enju (2):
igbvf: add lbtx_packets and lbtx_bytes to ethtool statistics
igbvf: remove redundant counter rx_long_byte_count from ethtool
statistics
drivers/net/ethernet/intel/igbvf/ethtool.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
--
2.48.1
next reply other threads:[~2025-08-18 15:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 15:18 Kohei Enju [this message]
2025-08-18 15:18 ` [PATCH v2 iwl-next 1/2] igbvf: add lbtx_packets and lbtx_bytes to ethtool statistics Kohei Enju
2025-08-19 8:17 ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-08-27 12:27 ` Simon Horman
2025-08-28 10:12 ` [Intel-wired-lan] " Romanowski, Rafal
2025-08-18 15:18 ` [PATCH v2 iwl-next 2/2] igbvf: remove redundant counter rx_long_byte_count from " Kohei Enju
2025-08-19 8:19 ` [Intel-wired-lan] " Loktionov, Aleksandr
2025-08-27 13:49 ` Simon Horman
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=20250818151902.64979-4-enjuk@amazon.com \
--to=enjuk@amazon.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).