From: Dragos Tatulea <dtatulea@nvidia.com>
To: Anshumali Gaur <agaur@marvell.com>,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] octeontx2-pf: persist netdev stats across routine operations
Date: Mon, 11 May 2026 12:03:32 +0200 [thread overview]
Message-ID: <bf626b44-efad-43f2-b8b4-509934f4befa@nvidia.com> (raw)
In-Reply-To: <20260511094205.1422268-1-agaur@marvell.com>
On 11.05.26 11:42, Anshumali Gaur wrote:
> Currently netdev driver is not retaining ethtool stats during
> interface up and down, as per kernel driver standard netdev driver
> must keep stats constant to avoid race conditions with user space
> trying to read them. Stats must persist across routine
> operations like bringing the interface down and up.
>
> Signed-off-by: Anshumali Gaur <agaur@marvell.com>
> ---
> v2:
> - Fix subject prefix to target net-next
> .../marvell/octeontx2/nic/otx2_common.c | 20 ++++++++++---------
> .../marvell/octeontx2/nic/otx2_common.h | 1 +
> .../ethernet/marvell/octeontx2/nic/otx2_pf.c | 18 +++++++++++++++++
> 3 files changed, 30 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.c b/drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.c
> index 971fcab1c248..0ffcc613a4b2 100644
> --- a/drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.c
> +++ b/drivers/net/ethernet/marvell/octeontx2/nic/otx2_common.c
> @@ -139,19 +139,21 @@ void otx2_get_stats64(struct net_device *netdev,
> struct rtnl_link_stats64 *stats)
> {
> struct otx2_nic *pfvf = netdev_priv(netdev);
> - struct otx2_dev_stats *dev_stats;
> + struct otx2_dev_stats *dev_stats, *old_stats;
>
> otx2_get_dev_stats(pfvf);
>
> dev_stats = &pfvf->hw.dev_stats;
> - stats->rx_bytes = dev_stats->rx_bytes;
> - stats->rx_packets = dev_stats->rx_frames;
> - stats->rx_dropped = dev_stats->rx_drops;
> - stats->multicast = dev_stats->rx_mcast_frames;
> -
> - stats->tx_bytes = dev_stats->tx_bytes;
> - stats->tx_packets = dev_stats->tx_frames;
> - stats->tx_dropped = dev_stats->tx_drops;
> + old_stats = &pfvf->hw.old_stats;
> +
> + stats->rx_bytes = old_stats->rx_bytes + dev_stats->rx_bytes;
> + stats->rx_packets = old_stats->rx_frames + dev_stats->rx_frames;
> + stats->rx_dropped = old_stats->rx_drops + dev_stats->rx_drops;
> + stats->multicast = old_stats->rx_mcast_frames + dev_stats->rx_mcast_frames;
> +
> + stats->tx_bytes = old_stats->tx_bytes + dev_stats->tx_bytes;
> + stats->tx_packets = old_stats->tx_frames + dev_stats->tx_frames;
> + stats->tx_dropped = old_stats->tx_drops + dev_stats->tx_drops;
I don't quite understand why the additional old_stats is required.
Why not accumulate dev_stats in place? Either directly in
otx2_get_dev_stats() or pass a local struct otx2_dev_stats var
and then accumulate that into dev_stats?
Thanks,
Dragos
next prev parent reply other threads:[~2026-05-11 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 9:42 [PATCH net-next v2] octeontx2-pf: persist netdev stats across routine operations Anshumali Gaur
2026-05-11 10:03 ` Dragos Tatulea [this message]
2026-05-12 0:12 ` Jakub Kicinski
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=bf626b44-efad-43f2-b8b4-509934f4befa@nvidia.com \
--to=dtatulea@nvidia.com \
--cc=agaur@marvell.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.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