From: "Nazle Asmade, Muhammad Nazim Amirul" <muhammad.nazim.amirul.nazle.asmade@altera.com>
To: Maxime Chevallier <maxime.chevallier@bootlin.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "andrew+netdev@lunn.ch" <andrew+netdev@lunn.ch>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"mcoquelin.stm32@gmail.com" <mcoquelin.stm32@gmail.com>,
"alexandre.torgue@foss.st.com" <alexandre.torgue@foss.st.com>,
"rmk+kernel@armlinux.org.uk" <rmk+kernel@armlinux.org.uk>,
"Jose.Abreu@synopsys.com" <Jose.Abreu@synopsys.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net: stmmac: xgmac2: disable RBUE in default RX interrupt mask
Date: Thu, 4 Jun 2026 09:47:02 +0000 [thread overview]
Message-ID: <f87b9bd6-4269-495f-b3c0-de402aeabbe1@altera.com> (raw)
In-Reply-To: <90716dc8-f10f-4777-9939-829f7e8b84ca@bootlin.com>
On 4/6/2026 5:08 pm, Maxime Chevallier wrote:
> Hi,
>
>>> to note that it'll
>>> now make the "rx_buf_unav_irq" stat (that we can query from userspace)
>>> stuck at 0 now.
>>>
>>> That's a user-visible behaviour change, for a stat that can be useful,
>>> one could consider that a uAPI change...
>>>
>>> Do you have some numbers on the perf impact you see when buffer
>>> starvation hits to see what we are gaining/losing here ?
>>>
>>> Maxime
>>>
>> Hi Maxime,
>>
>> Thank you for the review and for pointing out the rx_buf_unav_irq concern.
>>
>> We do have interrupt storm data to share. On Agilex5, under heavy RX
>> pressure we observed:
>>
>> Under heavy RX pressure we observed eth0:mac firing 1,821,811,555 times
>> vs 2,618,627 actual RX completions on eth0:rx-0 — a ~695x ratio.
>
> Ouch indeed. The stat itself has to stay, but the behaviour of that
> counter is already different depending on the DWMAC core version.
>
> I think we can get this patch in, but please state in the commit message
> the performance measurements you're mentioning, as well as the fact
> that the counter will now always show at 0 on XGMAC2 devices.
>
> Maybe we'll eventually need some switch to toggle these counters, as it's
> some valuable information when debugging, but has a significant impact on
> speeds.
>
> With the commit log updates,
>
> Reviewed-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
>
>>
>> BR,
>> Nazim
>
Hi Maxime,
Thanks for your review! Commit message now updated in v2
https://lore.kernel.org/all/20260604094512.21243-1-muhammad.nazim.amirul.nazle.asmade@altera.com/
BR,
Nazim
next prev parent reply other threads:[~2026-06-04 9:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 7:17 muhammad.nazim.amirul.nazle.asmade
2026-05-29 19:19 ` Maxime Chevallier
2026-06-04 9:01 ` Nazle Asmade, Muhammad Nazim Amirul
2026-06-04 9:08 ` Maxime Chevallier
2026-06-04 9:47 ` Nazle Asmade, Muhammad Nazim Amirul [this message]
2026-06-04 8:48 ` Paolo Abeni
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=f87b9bd6-4269-495f-b3c0-de402aeabbe1@altera.com \
--to=muhammad.nazim.amirul.nazle.asmade@altera.com \
--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=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
all inboxes | Powered by JetHome®