From: patchwork-bot+netdevbpf@kernel.org
To: Nazle@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org,
Asmade@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org,
Muhammad Nazim Amirul
<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: Fri, 12 Jun 2026 23:00:08 +0000 [thread overview]
Message-ID: <178130520813.1282281.6129214120774000716.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260609121703.9736-1-muhammad.nazim.amirul.nazle.asmade@altera.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 9 Jun 2026 05:17:03 -0700 you 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.
>
> [...]
Here is the summary with links:
- [v3] net: stmmac: xgmac2: disable RBUE in default RX interrupt mask
https://git.kernel.org/netdev/net-next/c/d3265c19b35d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-06-12 23:00 UTC|newest]
Thread overview: 3+ 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
2026-06-12 23:00 ` patchwork-bot+netdevbpf [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=178130520813.1282281.6129214120774000716.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Asmade@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=Jose.Abreu@synopsys.com \
--cc=Nazle@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--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