From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Jakub Kicinski <kuba@kernel.org>,
wen.yang@linux.dev, stable@vger.kernel.org,
linux-kernel@vger.kernel.org, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH 6.6 3/3] net: Allow to use SMP threads for backlog NAPI.
Date: Tue, 20 Jan 2026 07:03:58 +0100 [thread overview]
Message-ID: <2026012040-unmolded-dreaded-6e06@gregkh> (raw)
In-Reply-To: <20260119163026.aA1PeSmP@linutronix.de>
On Mon, Jan 19, 2026 at 05:30:26PM +0100, Sebastian Andrzej Siewior wrote:
> On 2026-01-19 08:25:34 [-0800], Jakub Kicinski wrote:
> > On Mon, 19 Jan 2026 00:15:46 +0800 wen.yang@linux.dev wrote:
> > > From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
> > >
> > > commit dad6b97702639fba27a2bd3e986982ad6f0db3a7 upstream.
> > >
> > > Backlog NAPI is a per-CPU NAPI struct only (with no device behind it)
> > > used by drivers which don't do NAPI them self, RPS and parts of the
> > > stack which need to avoid recursive deadlocks while processing a packet.
> >
> > This is a rather large change to backport into LTS.
>
> I agree. While I saw these patches flying by, I don't remember a mail
> where it was justified why it was needed. Did I miss it?
Please see patch 0/3 in this series:
https://lore.kernel.org/all/cover.1768751557.git.wen.yang@linux.dev/
next prev parent reply other threads:[~2026-01-20 6:04 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-18 16:15 [PATCH 6.6 0/3] net: Backlog NAPI threading for PREEMPT_RT wen.yang
2026-01-18 16:15 ` [PATCH 6.6 1/3] net: napi_schedule_rps() cleanup wen.yang
2026-01-18 16:17 ` [PATCH 6.1 " wen.yang
2026-01-18 16:28 ` wen.yang
2026-01-18 16:15 ` [PATCH 6.6 2/3] net: Remove conditional threaded-NAPI wakeup based on task state wen.yang
2026-01-18 16:17 ` [PATCH 6.1 " wen.yang
2026-01-18 16:28 ` wen.yang
2026-01-18 16:15 ` [PATCH 6.6 3/3] net: Allow to use SMP threads for backlog NAPI wen.yang
2026-01-18 16:17 ` [PATCH 6.1 " wen.yang
2026-01-18 16:28 ` wen.yang
2026-01-18 16:31 ` wen.yang
2026-01-19 16:25 ` [PATCH 6.6 " Jakub Kicinski
2026-01-19 16:30 ` Sebastian Andrzej Siewior
2026-01-20 6:03 ` Greg Kroah-Hartman [this message]
2026-01-20 8:01 ` Sebastian Andrzej Siewior
2026-01-20 9:21 ` Greg Kroah-Hartman
2026-01-20 10:38 ` Sebastian Andrzej Siewior
2026-02-04 13:54 ` Greg Kroah-Hartman
2026-02-07 20:26 ` Wen Yang
2026-01-18 16:17 ` [PATCH 6.1 0/3] net: Backlog NAPI threading for PREEMPT_RT wen.yang
2026-01-18 16:28 ` wen.yang
2026-01-18 17:02 ` [PATCH 6.6 " Wen Yang
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=2026012040-unmolded-dreaded-6e06@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=bigeasy@linutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--cc=wen.yang@linux.dev \
/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