From: Simon Horman <horms@kernel.org>
To: muhammad.nazim.amirul.nazle.asmade@altera.com
Cc: netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, mcoquelin.stm32@gmail.com,
alexandre.torgue@foss.st.com, rmk+kernel@armlinux.org.uk,
maxime.chevallier@bootlin.com, Jose.Abreu@synopsys.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] net: stmmac: xgmac2: disable RBUE in default RX interrupt mask
Date: Thu, 11 Jun 2026 17:44:14 +0100 [thread overview]
Message-ID: <20260611164414.GX3920875@horms.kernel.org> (raw)
In-Reply-To: <20260609121703.9736-1-muhammad.nazim.amirul.nazle.asmade@altera.com>
On Tue, Jun 09, 2026 at 05:17:03AM -0700, muhammad.nazim.amirul.nazle.asmade@altera.com wrote:
> From: Nazim Amirul <muhammad.nazim.amirul.nazle.asmade@altera.com>
>
> Enabling the RX Buffer Unavailable (RBUE) interrupt is counterproductive
> and can trigger a MAC interrupt storm under heavy RX pressure. When the
> DMA runs out of RX descriptors it fires RBUE continuously until software
> refills the ring.
>
> However, RBUE is redundant: the normal RX completion interrupt (RIE)
> already triggers NAPI, which processes completed descriptors and refills
> the ring, causing the DMA to resume. The RBUE handler itself only sets
> handle_rx - the same outcome as RIE.
>
> On Agilex5 under heavy RX pressure, the MAC interrupt (which includes
> RBUE) was observed firing 1,821,811,555 times against only 2,618,627
> actual RX completions - a ~695x ratio - confirming the severity of the
> storm.
>
> RBUE does not provide OOM recovery. If page_pool is exhausted,
> stmmac_rx_refill() cannot advance the DMA tail pointer, the DMA stays
> suspended, and RBUE fires again on the next NAPI completion - a storm
> with no forward progress. This patch trades that storm for a clean
> stall with the same RX outcome. Proper OOM recovery is a pre-existing
> gap outside the scope of this fix.
>
> Note: as a consequence of disabling RBUE, the rx_buf_unav_irq ethtool
> counter will always read 0 on XGMAC2 devices. This behaviour is already
> inconsistent across DWMAC core versions.
>
> Remove RBUE from XGMAC_DMA_INT_DEFAULT_EN and XGMAC_DMA_INT_DEFAULT_RX
> to prevent the interrupt storm while keeping normal RX handling intact.
>
> Fixes: d6ddfacd95c7 ("net: stmmac: Add DMA related callbacks for XGMAC2")
> Reviewed-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
> Signed-off-by: Nazim Amirul <muhammad.nazim.amirul.nazle.asmade@altera.com>
> ---
> Changes in v3:
> - Clarified that RBUE does not provide OOM recovery even when enabled;
> disabling it trades an interrupt storm for a clean stall with the same
> RX outcome (Simon Horman, Paolo Abeni)
Reviewed-by: Simon Horman <horms@kernel.org>
prev parent reply other threads:[~2026-06-11 16:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 12:17 [PATCH v3] net: stmmac: xgmac2: disable RBUE in default RX interrupt mask muhammad.nazim.amirul.nazle.asmade
2026-06-11 16:44 ` Simon Horman [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=20260611164414.GX3920875@horms.kernel.org \
--to=horms@kernel.org \
--cc=Jose.Abreu@synopsys.com \
--cc=alexandre.torgue@foss.st.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=maxime.chevallier@bootlin.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=muhammad.nazim.amirul.nazle.asmade@altera.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rmk+kernel@armlinux.org.uk \
/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