From: Paul Menzel <pmenzel@molgen.mpg.de>
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
Subject: Re: [Intel-wired-lan] [PATCH v1 iwl-next 2/2] igbvf: remove duplicated counter rx_long_byte_count from ethtool statistics
Date: Wed, 13 Aug 2025 10:20:33 +0200 [thread overview]
Message-ID: <785b380c-d4ba-423c-93ed-059d0aebc6be@molgen.mpg.de> (raw)
In-Reply-To: <20250813075206.70114-3-enjuk@amazon.com>
Dear Kohei,
Thank you for your patch.
Am 13.08.25 um 09:50 schrieb Kohei Enju:
> rx_long_byte_count shows the value of the GORC (Good Octets Received
> Count) register. However, the register value is already shown as
> rx_bytes and they always show the same value.
>
> Remove rx_long_byte_count as the Intel ethernet driver e1000e did in
> commit 0a939912cf9c ("e1000e: cleanup redundant statistics counter").
>
> Tested on Intel Corporation I350 Gigabit Network Connection.
>
> Tested-by: Kohei Enju <enjuk@amazon.com>
> Signed-off-by: Kohei Enju <enjuk@amazon.com>
> ---
> drivers/net/ethernet/intel/igbvf/ethtool.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/intel/igbvf/ethtool.c b/drivers/net/ethernet/intel/igbvf/ethtool.c
> index c6defc495f13..9c08ebfad804 100644
> --- a/drivers/net/ethernet/intel/igbvf/ethtool.c
> +++ b/drivers/net/ethernet/intel/igbvf/ethtool.c
> @@ -36,7 +36,6 @@ static const struct igbvf_stats igbvf_gstrings_stats[] = {
> { "lbtx_bytes", IGBVF_STAT(stats.gotlbc, stats.base_gotlbc) },
> { "tx_restart_queue", IGBVF_STAT(restart_queue, zero_base) },
> { "tx_timeout_count", IGBVF_STAT(tx_timeout_count, zero_base) },
> - { "rx_long_byte_count", IGBVF_STAT(stats.gorc, stats.base_gorc) },
> { "rx_csum_offload_good", IGBVF_STAT(hw_csum_good, zero_base) },
> { "rx_csum_offload_errors", IGBVF_STAT(hw_csum_err, zero_base) },
> { "rx_header_split", IGBVF_STAT(rx_hdr_split, zero_base) },
Reviewed-by: Paul Menzel <pmenzel@molgen.mpg.de>
Kind regards,
Paul
PS: Should you resend, *redundant* instead of *duplicated* might better
describe the removed counter.
next prev parent reply other threads:[~2025-08-13 8:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 7:50 [PATCH v1 iwl-next 0/2] igbvf: ethtool statistics improvements Kohei Enju
2025-08-13 7:50 ` [PATCH v1 iwl-next 1/2] igbvf: add lbtx_packets and lbtx_bytes to ethtool statistics Kohei Enju
2025-08-13 8:18 ` [Intel-wired-lan] " Paul Menzel
2025-08-13 8:47 ` Kohei Enju
2025-08-26 15:51 ` Simon Horman
2025-08-28 10:16 ` Romanowski, Rafal
2025-08-13 7:50 ` [PATCH v1 iwl-next 2/2] igbvf: remove duplicated counter rx_long_byte_count from " Kohei Enju
2025-08-13 8:20 ` Paul Menzel [this message]
2025-08-13 8:54 ` [Intel-wired-lan] " Kohei Enju
2025-08-26 15:52 ` 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=785b380c-d4ba-423c-93ed-059d0aebc6be@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--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=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).