All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jisheng Zhang <jszhang@kernel.org>
To: "Petr Tesařík" <petr@tesarici.cz>
Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>,
	Jose Abreu <joabreu@synopsys.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Chen-Yu Tsai <wens@csie.org>,
	Jernej Skrabec <jernej.skrabec@gmail.com>,
	Samuel Holland <samuel@sholland.org>,
	"open list:STMMAC ETHERNET DRIVER" <netdev@vger.kernel.org>,
	"moderated list:ARM/STM32 ARCHITECTURE"
	<linux-stm32@st-md-mailman.stormreply.com>,
	"moderated list:ARM/STM32 ARCHITECTURE"
	<linux-arm-kernel@lists.infradead.org>,
	open list <linux-kernel@vger.kernel.org>,
	"open list:ARM/Allwinner sunXi SoC support"
	<linux-sunxi@lists.linux.dev>,
	Marc Haber <mh+netdev@zugschlus.de>, Andrew Lunn <andrew@lunn.ch>,
	Florian Fainelli <f.fainelli@gmail.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH net v2] net: stmmac: protect updates of 64-bit statistics counters
Date: Tue, 30 Jan 2024 19:39:35 +0800	[thread overview]
Message-ID: <Zbjf9yQRV26EO7le@xhacker> (raw)
In-Reply-To: <20240130083539.4ea26a8d@meshulam.tesarici.cz>

On Tue, Jan 30, 2024 at 08:35:39AM +0100, Petr Tesařík wrote:
> On Tue, 30 Jan 2024 13:00:10 +0800
> Jisheng Zhang <jszhang@kernel.org> wrote:
> 
> > On Sun, Jan 28, 2024 at 08:35:29PM +0100, Petr Tesarik wrote:
> > > As explained by a comment in <linux/u64_stats_sync.h>, write side of struct
> > > u64_stats_sync must ensure mutual exclusion, or one seqcount update could
> > > be lost on 32-bit platforms, thus blocking readers forever. Such lockups
> > > have been observed in real world after stmmac_xmit() on one CPU raced with
> > > stmmac_napi_poll_tx() on another CPU.
> > > 
> > > To fix the issue without introducing a new lock, split the statics into
> > > three parts:
> > > 
> > > 1. fields updated only under the tx queue lock,
> > > 2. fields updated only during NAPI poll,
> > > 3. fields updated only from interrupt context,
> > > 
> > > Updates to fields in the first two groups are already serialized through
> > > other locks. It is sufficient to split the existing struct u64_stats_sync
> > > so that each group has its own.
> > > 
> > > Note that tx_set_ic_bit is updated from both contexts. Split this counter
> > > so that each context gets its own, and calculate their sum to get the total
> > > value in stmmac_get_ethtool_stats().
> > > 
> > > For the third group, multiple interrupts may be processed by different CPUs
> > > at the same time, but interrupts on the same CPU will not nest. Move fields
> > > from this group to a newly created per-cpu struct stmmac_pcpu_stats.
> > > 
> > > Fixes: 133466c3bbe1 ("net: stmmac: use per-queue 64 bit statistics where necessary")
> > > Link: https://lore.kernel.org/netdev/Za173PhviYg-1qIn@torres.zugschlus.de/t/
> > > Cc: stable@vger.kernel.org
> > > Signed-off-by: Petr Tesarik <petr@tesarici.cz>  
> > 
> > Thanks for the fix patch. One trivial improviement below
> > s/netdev_alloc_pcpu_stats/devm_netdev_alloc_pcpu_stats to simplify
> > error and exit code path.
> 
> Thanks for your review.
> 
> In fact, many other allocations in stmmac could be converted to devm_*.
> I wanted to stay consistent with the existing code, but hey, you're

there's already devm_* usage in stmmac_dvr_probe(), eg. devm_alloc_etherdev_mqs
I believe other parts are from the old days when there's no devm_* APIs

> right there's no good reason for it.
> 
> Plus, I can send convert the other places with another patch.
> 
> > With that:
> > Reviewed-by: Jisheng Zhang <jszhang@kernel.org>
> > 
> > PS: when I sent the above "net: stmmac: use per-queue 64 bit statistics
> > where necessary", I had an impression: there are too much statistics in
> > stmmac driver, I didn't see so many statistics in other eth drivers, is
> > it possible to remove some useless or not that useful statistic members?
> 
> I don't feel authorized to make the decision. But I also wonder about
> some counters. For example, why is there tx_packets and tx_pkt_n? The
> former is shown as RX packets by "ip stats show dev end0", the latter
> is shown by as tx_pkt_n by "ethtools -S end0". The values do differ,
> but I have no clue why, and if they are even expected to be different
> or if it's a bug.
> 
> Petr T

WARNING: multiple messages have this Message-ID (diff)
From: Jisheng Zhang <jszhang@kernel.org>
To: "Petr Tesařík" <petr@tesarici.cz>
Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>,
	Jose Abreu <joabreu@synopsys.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	Chen-Yu Tsai <wens@csie.org>,
	Jernej Skrabec <jernej.skrabec@gmail.com>,
	Samuel Holland <samuel@sholland.org>,
	"open list:STMMAC ETHERNET DRIVER" <netdev@vger.kernel.org>,
	"moderated list:ARM/STM32 ARCHITECTURE"
	<linux-stm32@st-md-mailman.stormreply.com>,
	"moderated list:ARM/STM32 ARCHITECTURE"
	<linux-arm-kernel@lists.infradead.org>,
	open list <linux-kernel@vger.kernel.org>,
	"open list:ARM/Allwinner sunXi SoC support"
	<linux-sunxi@lists.linux.dev>,
	Marc Haber <mh+netdev@zugschlus.de>, Andrew Lunn <andrew@lunn.ch>,
	Florian Fainelli <f.fainelli@gmail.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH net v2] net: stmmac: protect updates of 64-bit statistics counters
Date: Tue, 30 Jan 2024 19:39:35 +0800	[thread overview]
Message-ID: <Zbjf9yQRV26EO7le@xhacker> (raw)
In-Reply-To: <20240130083539.4ea26a8d@meshulam.tesarici.cz>

On Tue, Jan 30, 2024 at 08:35:39AM +0100, Petr Tesařík wrote:
> On Tue, 30 Jan 2024 13:00:10 +0800
> Jisheng Zhang <jszhang@kernel.org> wrote:
> 
> > On Sun, Jan 28, 2024 at 08:35:29PM +0100, Petr Tesarik wrote:
> > > As explained by a comment in <linux/u64_stats_sync.h>, write side of struct
> > > u64_stats_sync must ensure mutual exclusion, or one seqcount update could
> > > be lost on 32-bit platforms, thus blocking readers forever. Such lockups
> > > have been observed in real world after stmmac_xmit() on one CPU raced with
> > > stmmac_napi_poll_tx() on another CPU.
> > > 
> > > To fix the issue without introducing a new lock, split the statics into
> > > three parts:
> > > 
> > > 1. fields updated only under the tx queue lock,
> > > 2. fields updated only during NAPI poll,
> > > 3. fields updated only from interrupt context,
> > > 
> > > Updates to fields in the first two groups are already serialized through
> > > other locks. It is sufficient to split the existing struct u64_stats_sync
> > > so that each group has its own.
> > > 
> > > Note that tx_set_ic_bit is updated from both contexts. Split this counter
> > > so that each context gets its own, and calculate their sum to get the total
> > > value in stmmac_get_ethtool_stats().
> > > 
> > > For the third group, multiple interrupts may be processed by different CPUs
> > > at the same time, but interrupts on the same CPU will not nest. Move fields
> > > from this group to a newly created per-cpu struct stmmac_pcpu_stats.
> > > 
> > > Fixes: 133466c3bbe1 ("net: stmmac: use per-queue 64 bit statistics where necessary")
> > > Link: https://lore.kernel.org/netdev/Za173PhviYg-1qIn@torres.zugschlus.de/t/
> > > Cc: stable@vger.kernel.org
> > > Signed-off-by: Petr Tesarik <petr@tesarici.cz>  
> > 
> > Thanks for the fix patch. One trivial improviement below
> > s/netdev_alloc_pcpu_stats/devm_netdev_alloc_pcpu_stats to simplify
> > error and exit code path.
> 
> Thanks for your review.
> 
> In fact, many other allocations in stmmac could be converted to devm_*.
> I wanted to stay consistent with the existing code, but hey, you're

there's already devm_* usage in stmmac_dvr_probe(), eg. devm_alloc_etherdev_mqs
I believe other parts are from the old days when there's no devm_* APIs

> right there's no good reason for it.
> 
> Plus, I can send convert the other places with another patch.
> 
> > With that:
> > Reviewed-by: Jisheng Zhang <jszhang@kernel.org>
> > 
> > PS: when I sent the above "net: stmmac: use per-queue 64 bit statistics
> > where necessary", I had an impression: there are too much statistics in
> > stmmac driver, I didn't see so many statistics in other eth drivers, is
> > it possible to remove some useless or not that useful statistic members?
> 
> I don't feel authorized to make the decision. But I also wonder about
> some counters. For example, why is there tx_packets and tx_pkt_n? The
> former is shown as RX packets by "ip stats show dev end0", the latter
> is shown by as tx_pkt_n by "ethtools -S end0". The values do differ,
> but I have no clue why, and if they are even expected to be different
> or if it's a bug.
> 
> Petr T

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2024-01-30 11:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-28 19:35 [PATCH net v2] net: stmmac: protect updates of 64-bit statistics counters Petr Tesarik
2024-01-28 19:35 ` Petr Tesarik
2024-01-30  5:00 ` Jisheng Zhang
2024-01-30  5:00   ` Jisheng Zhang
2024-01-30  7:35   ` Petr Tesařík
2024-01-30  7:35     ` Petr Tesařík
2024-01-30 11:39     ` Jisheng Zhang [this message]
2024-01-30 11:39       ` Jisheng Zhang
2024-01-30 13:48   ` Andrew Lunn
2024-01-30 13:48     ` Andrew Lunn

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=Zbjf9yQRV26EO7le@xhacker \
    --to=jszhang@kernel.org \
    --cc=alexandre.torgue@foss.st.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=jernej.skrabec@gmail.com \
    --cc=joabreu@synopsys.com \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=mh+netdev@zugschlus.de \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=petr@tesarici.cz \
    --cc=samuel@sholland.org \
    --cc=stable@vger.kernel.org \
    --cc=wens@csie.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.