From: Larysa Zaremba <larysa.zaremba@intel.com>
To: Shinas Rasheed <srasheed@marvell.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Haseeb Gani <hgani@marvell.com>,
Sathesh B Edara <sedara@marvell.com>,
Vimlesh Kumar <vimleshk@marvell.com>,
"thaller@redhat.com" <thaller@redhat.com>,
"wizhao@redhat.com" <wizhao@redhat.com>,
"kheib@redhat.com" <kheib@redhat.com>,
"konguyen@redhat.com" <konguyen@redhat.com>,
"horms@kernel.org" <horms@kernel.org>,
"einstein.xue@synaxg.com" <einstein.xue@synaxg.com>,
Veerasenareddy Burru <vburru@marvell.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>,
Satananda Burla <sburla@marvell.com>,
Abhijit Ayarekar <aayarekar@marvell.com>
Subject: Re: [EXTERNAL] Re: [PATCH net v2 2/4] octeon_ep: remove firmware stats fetch in ndo_get_stats64
Date: Tue, 17 Dec 2024 17:37:20 +0100 [thread overview]
Message-ID: <Z2GowEuPU0nILAoW@lzaremba-mobl.ger.corp.intel.com> (raw)
In-Reply-To: <BY3PR18MB4721878201E1B93AFB29367EC73B2@BY3PR18MB4721.namprd18.prod.outlook.com>
On Mon, Dec 16, 2024 at 06:31:05PM +0000, Shinas Rasheed wrote:
> Hi Larysa,
>
>
> > On Sun, Dec 15, 2024 at 11:58:40PM -0800, Shinas Rasheed wrote:
> > > The per queue stats are available already and are retrieved
> > > from register reads during ndo_get_stats64. The firmware stats
> > > fetch call that happens in ndo_get_stats64() is currently not
> > > required
> > >
> > > Fixes: 6a610a46bad1 ("octeon_ep: add support for ndo ops")
> > > Signed-off-by: Shinas Rasheed <srasheed@marvell.com>
> > > @@ -1019,10 +1013,6 @@ static void octep_get_stats64(struct net_device
> > *netdev,
> > > stats->tx_bytes = tx_bytes;
> > > stats->rx_packets = rx_packets;
> > > stats->rx_bytes = rx_bytes;
> > > - stats->multicast = oct->iface_rx_stats.mcast_pkts;
> > > - stats->rx_errors = oct->iface_rx_stats.err_pkts;
> > > - stats->collisions = oct->iface_tx_stats.xscol;
> > > - stats->tx_fifo_errors = oct->iface_tx_stats.undflw;
> >
> > I do not see, how it is a fix to remove some fields from stats. If this is a
> > cleanup, it should not go to the stable tree.
> >
> > > }
> > >
>
> The fix part of this patch is to remove the call to firmware to retrieve stats, which could block and cause rcu read lock warnings.
> The fields that are retrieved by this stats call can be neglected for use cases concerning the DPU, and the necessary stats are already
> read from per queue hardware stats registers. Hence, why the code is removed.
>
Please, provide the warinings in question in the commit message, this is an
important context for anyone that would need to look through code history.
next prev parent reply other threads:[~2024-12-17 16:38 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 7:58 [PATCH net v2 0/4] Fix race conditions " Shinas Rasheed
2024-12-16 7:58 ` [PATCH net v2 1/4] octeon_ep: fix " Shinas Rasheed
2024-12-16 14:30 ` Larysa Zaremba
2024-12-16 14:46 ` Larysa Zaremba
2024-12-16 18:28 ` [EXTERNAL] " Shinas Rasheed
2024-12-17 17:06 ` Larysa Zaremba
2024-12-17 17:49 ` Shinas Rasheed
2024-12-18 13:25 ` Larysa Zaremba
2024-12-18 13:58 ` Shinas Rasheed
2024-12-18 14:21 ` Eric Dumazet
2024-12-18 14:49 ` Larysa Zaremba
2024-12-18 15:03 ` Eric Dumazet
2024-12-18 15:25 ` Shinas Rasheed
2024-12-18 15:39 ` Eric Dumazet
2024-12-19 16:28 ` Shinas Rasheed
2024-12-19 16:35 ` Eric Dumazet
2024-12-16 18:24 ` Shinas Rasheed
2024-12-16 7:58 ` [PATCH net v2 2/4] octeon_ep: remove firmware stats fetch " Shinas Rasheed
2024-12-16 14:40 ` Larysa Zaremba
2024-12-16 18:31 ` [EXTERNAL] " Shinas Rasheed
2024-12-17 16:37 ` Larysa Zaremba [this message]
2024-12-16 7:58 ` [PATCH net v2 3/4] octeon_ep_vf: fix race conditions " Shinas Rasheed
2024-12-16 7:58 ` [PATCH net v2 4/4] octeon_ep_vf: remove firmware stats fetch " Shinas Rasheed
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=Z2GowEuPU0nILAoW@lzaremba-mobl.ger.corp.intel.com \
--to=larysa.zaremba@intel.com \
--cc=aayarekar@marvell.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=einstein.xue@synaxg.com \
--cc=hgani@marvell.com \
--cc=horms@kernel.org \
--cc=kheib@redhat.com \
--cc=konguyen@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sburla@marvell.com \
--cc=sedara@marvell.com \
--cc=srasheed@marvell.com \
--cc=thaller@redhat.com \
--cc=vburru@marvell.com \
--cc=vimleshk@marvell.com \
--cc=wizhao@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
all inboxes | Powered by JetHome®