From: Jakub Kicinski <kuba@kernel.org>
To: Dragos Tatulea <dtatulea@nvidia.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Martin Karsten <mkarsten@uwaterloo.ca>,
Gal Pressman <gal@nvidia.com>, Tariq Toukan <tariqt@nvidia.com>,
Joe Damato <joe@dama.to>,
Frederik Deweerdt <fdeweerdt@fastly.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH net-next 2/2] net: napi: Skip poll when arming GRO timer in busy poll
Date: Tue, 28 Apr 2026 17:37:34 -0700 [thread overview]
Message-ID: <20260428173734.7f4ee58d@kernel.org> (raw)
In-Reply-To: <20260428175134.1197036-4-dtatulea@nvidia.com>
On Tue, 28 Apr 2026 17:51:31 +0000 Dragos Tatulea wrote:
> From: Martin Karsten <mkarsten@uwaterloo.ca>
>
> As referenced in the previous patch, having the GRO timer scheduled
> while poll is running can lead to issues.
>
> Skip the extra call to napi->poll() when the GRO timer is armed. This
> removes the need for having a separate __busy_poll_stop routine and its
> code is moved directly into the relevant places in busy_poll_stop.
This needs to go in separately, the previous patch should be a Fix,
this is net-next material.
> @@ -6918,13 +6898,28 @@ static void busy_poll_stop(struct napi_struct *napi, void *have_poll_lock,
>
> if (flags & NAPI_F_PREFER_BUSY_POLL) {
> napi->defer_hard_irqs_count = napi_get_defer_hard_irqs(napi);
> - if (napi->defer_hard_irqs_count) {
> - /* Timer will be scheduled after napi poll to avoid
> - * firing during a slow poll which could cause the
> - * queue to get stuck with interrupts disabled and no
> - * scheduled timer.
> + timeout = napi_get_gro_flush_timeout(napi);
> + if (napi->defer_hard_irqs_count && timeout) {
> + unsigned long flags;
Feels like either timeout should also be declared in closest scope or
flags at function level
> + /* Drop prefer-busy state as in napi_complete_done(). */
sloppy comment
> + clear_bit(NAPI_STATE_PREFER_BUSY_POLL, &napi->state);
> + netpoll_poll_unlock(have_poll_lock);
> +
> + /* Flush too old packets. If HZ < 1000, flush all
> + * packets.
> + */
sloppy comment
> + gro_flush_normal(&napi->gro, HZ >= 1000);
> + local_irq_save(flags);
> + hrtimer_start(&napi->timer, ns_to_ktime(timeout),
> + HRTIMER_MODE_REL_PINNED);
> + clear_bit(NAPI_STATE_SCHED, &napi->state);
> + local_irq_restore(flags);
> +
> + /* Timer started, so need for another call to
> + * napi->poll().
> */
> - timeout = napi_get_gro_flush_timeout(napi);
> + goto out;
I think an else branch would do here? Let's not abuse goto
> }
> }
>
> @@ -6938,8 +6933,12 @@ static void busy_poll_stop(struct napi_struct *napi, void *have_poll_lock,
> */
> trace_napi_poll(napi, rc, budget);
> netpoll_poll_unlock(have_poll_lock);
> - if (rc == budget)
> - __busy_poll_stop(napi, timeout);
> + if (rc == budget) {
> + gro_normal_list(&napi->gro);
> + __napi_schedule(napi);
> + }
> +
> +out:
> bpf_net_ctx_clear(bpf_net_ctx);
> local_bh_enable();
> }
next prev parent reply other threads:[~2026-04-29 0:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 17:51 [RFC PATCH net-next 0/2] net: napi: Fix timer arming during busy poll timeout Dragos Tatulea
2026-04-28 17:51 ` [RFC PATCH net-next 1/2] net: napi: Fix interrupts permanently disabled during busy poll Dragos Tatulea
2026-04-28 23:40 ` Jakub Kicinski
2026-04-29 0:04 ` Martin Karsten
2026-04-29 0:31 ` Jakub Kicinski
2026-04-29 8:13 ` Dragos Tatulea
2026-04-29 22:52 ` Jakub Kicinski
2026-04-29 0:38 ` Jakub Kicinski
2026-04-29 8:43 ` Dragos Tatulea
2026-04-29 12:13 ` Björn Töpel
2026-04-29 12:43 ` Dragos Tatulea
2026-05-04 11:30 ` Dragos Tatulea
2026-05-05 1:00 ` Jakub Kicinski
2026-04-28 17:51 ` [RFC PATCH net-next 2/2] net: napi: Skip poll when arming GRO timer in " Dragos Tatulea
2026-04-29 0:37 ` Jakub Kicinski [this message]
2026-04-29 1:02 ` Martin Karsten
2026-04-29 12:37 ` Björn Töpel
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=20260428173734.7f4ee58d@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=dtatulea@nvidia.com \
--cc=edumazet@google.com \
--cc=fdeweerdt@fastly.com \
--cc=gal@nvidia.com \
--cc=horms@kernel.org \
--cc=joe@dama.to \
--cc=linux-kernel@vger.kernel.org \
--cc=mkarsten@uwaterloo.ca \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tariqt@nvidia.com \
/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