From: Jacob Keller <jacob.e.keller@intel.com>
To: <muhammad.nazim.amirul.nazle.asmade@altera.com>,
<netdev@vger.kernel.org>
Cc: <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>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] net: stmmac: Improve Tx timer arm logic further
Date: Wed, 27 May 2026 14:00:03 -0700 [thread overview]
Message-ID: <f6eca916-72a7-44cf-bdaf-4a4a06294023@intel.com> (raw)
In-Reply-To: <20260527023359.18876-1-muhammad.nazim.amirul.nazle.asmade@altera.com>
On 5/26/2026 7:33 PM, muhammad.nazim.amirul.nazle.asmade@altera.com wrote:
> From: Nazim Amirul <muhammad.nazim.amirul.nazle.asmade@altera.com>
>
> Calling hrtimer_start() on an already-active txtimer is unnecessary
> and expensive. Skip the restart if the timer is already active by
> adding an hrtimer_active() check before hrtimer_start().
>
> This avoids redundant timer restarts under burst traffic and ensures
> NAPI is scheduled within tx_coal_timer microseconds of the first
> packet rather than having the window reset on every packet.
>
> There is no race concern: hrtimer_start() is internally serialized and
> safe to call on an active timer. In the event of a race between
> hrtimer_active() and hrtimer_start(), the worst case is calling
> hrtimer_start() on an already-active timer, which is identical to the
> pre-patch behaviour. The meaning of tx_coal_timer is unchanged.
>
> Performance on Cyclone V with dwmac-socfpga (iperf3 -u -b 0 -l 64):
> Before: ~45200 pps
> After: ~52300 pps (~15% improvement)
>
> Additionally, ~10% improvement in UDP throughput observed on Agilex5,
> with hrtimer CPU usage reduced from ~8% to ~0.6%.
>
Nice improvements! Appreciate seeing the data here.
Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>
> Signed-off-by: Rohan G Thomas <rohan.g.thomas@altera.com>
> Tested-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
> Reviewed-by: Maxime Chevallier <maxime.chevallier@bootlin.com>
> Signed-off-by: Nazim Amirul <muhammad.nazim.amirul.nazle.asmade@altera.com>
> ---
> Changes in v2:
> - Expanded commit message to address race condition concern and clarify
> tx_coal_timer semantics (Andrew Lunn)
> - Added performance numbers to commit message (Andrew Lunn)
> - Added Agilex5 performance data with hrtimer CPU usage improvement
> - Added Tested-by and Reviewed-by from Maxime Chevallier
> ---
> drivers/net/ethernet/stmicro/stmmac/stmmac_main.c | 12 +++++++-----
> 1 file changed, 7 insertions(+), 5 deletions()
>
> diff --git a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
> index 3591755ea30b..35da51c26248 100644
> --- a/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
> +++ b/drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
> @@ -3341,12 +3341,14 @@ static void stmmac_tx_timer_arm(struct stmmac_priv *priv, u32 queue)
> * Try to cancel any timer if napi is scheduled, timer will be armed
> * again in the next scheduled napi.
> */
> - if (unlikely(!napi_is_scheduled(napi)))
> - hrtimer_start(&tx_q->txtimer,
> - STMMAC_COAL_TIMER(tx_coal_timer),
> - HRTIMER_MODE_REL);
> - else
> + if (unlikely(!napi_is_scheduled(napi))) {
> + if (unlikely(!(hrtimer_active(&tx_q->txtimer))))
> + hrtimer_start(&tx_q->txtimer,
> + STMMAC_COAL_TIMER(tx_coal_timer),
> + HRTIMER_MODE_REL);
> + } else {
> hrtimer_try_to_cancel(&tx_q->txtimer);
> + }
> }
>
> /**
next prev parent reply other threads:[~2026-05-27 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 2:33 muhammad.nazim.amirul.nazle.asmade
2026-05-27 21:00 ` Jacob Keller [this message]
2026-05-28 1:58 ` Andrew Lunn
2026-05-29 6:47 ` Nazle Asmade, Muhammad Nazim Amirul
-- strict thread matches above, loose matches on Subject: below --
2026-05-26 5:19 muhammad.nazim.amirul.nazle.asmade
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=f6eca916-72a7-44cf-bdaf-4a4a06294023@intel.com \
--to=jacob.e.keller@intel.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-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--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
all inboxes | Powered by JetHome®