From: Paolo Abeni <pabeni@redhat.com>
To: Anshumali Gaur <agaur@marvell.com>,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, gakula@marvell.com, hkelam@marvell.com,
sbhatta@marvell.com, sgoutham@marvell.com, bbhushan2@marvell.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v4] octeontx2-pf: Retain ethtool stats across interface down/up.
Date: Tue, 19 May 2026 11:44:46 +0200 [thread overview]
Message-ID: <5e306e50-bced-4d4d-9eb4-766224680145@redhat.com> (raw)
In-Reply-To: <20260514091634.1611537-1-agaur@marvell.com>
On 5/14/26 11:16 AM, Anshumali Gaur wrote:
> 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;
Please respect the reverse christmas tree order above.
> diff --git a/drivers/net/ethernet/marvell/octeontx2/nic/otx2_pf.c b/drivers/net/ethernet/marvell/octeontx2/nic/otx2_pf.c
> index ee623476e5ff..21fd1dd4d755 100644
> --- a/drivers/net/ethernet/marvell/octeontx2/nic/otx2_pf.c
> +++ b/drivers/net/ethernet/marvell/octeontx2/nic/otx2_pf.c
> @@ -2154,6 +2154,8 @@ EXPORT_SYMBOL(otx2_open);
> int otx2_stop(struct net_device *netdev)
> {
> struct otx2_nic *pf = netdev_priv(netdev);
> + struct otx2_dev_stats *old_stats = &pf->hw.old_stats;
> + struct otx2_dev_stats *dev = &pf->hw.dev_stats;
> struct otx2_cq_poll *cq_poll = NULL;
> struct otx2_qset *qset = &pf->qset;
> int qidx, vec, wrk;
Same here. You need to split variable declaration and initialization.
> @@ -2162,6 +2164,27 @@ int otx2_stop(struct net_device *netdev)
> if (pf->flags & OTX2_FLAG_INTF_DOWN)
> return 0;
>
> + /* First stop packet Rx/Tx */
> + otx2_rxtx_enable(pf, false);
> +
> + /* Read final HW counters and accumulate */
> + otx2_get_dev_stats(pf);
> +
> + /* Accumulate old stats */
> + old_stats->rx_bytes += dev->rx_bytes;
> + old_stats->rx_drops += dev->rx_drops;
> + old_stats->rx_bcast_frames += dev->rx_bcast_frames;
> + old_stats->rx_mcast_frames += dev->rx_mcast_frames;
> + old_stats->rx_ucast_frames += dev->rx_ucast_frames;
> + old_stats->rx_frames += dev->rx_frames;
> +
> + old_stats->tx_bytes += dev->tx_bytes;
> + old_stats->tx_drops += dev->tx_drops;
> + old_stats->tx_bcast_frames += dev->tx_bcast_frames;
> + old_stats->tx_mcast_frames += dev->tx_mcast_frames;
> + old_stats->tx_ucast_frames += dev->tx_ucast_frames;
> + old_stats->tx_frames += dev->tx_frames;
Sashiko notes this is still racy, as napi can still run and update the
counters. You should move the stat collection just before freeing H/W
resources.
/P
prev parent reply other threads:[~2026-05-19 9:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 9:16 Anshumali Gaur
2026-05-19 9:44 ` Paolo Abeni [this message]
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=5e306e50-bced-4d4d-9eb4-766224680145@redhat.com \
--to=pabeni@redhat.com \
--cc=agaur@marvell.com \
--cc=andrew+netdev@lunn.ch \
--cc=bbhushan2@marvell.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.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
all inboxes | Powered by JetHome®