public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
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: Wed, 4 Feb 2026 14:54:59 +0100	[thread overview]
Message-ID: <2026020449-deplete-swoosh-2387@gregkh> (raw)
In-Reply-To: <20260120103833.4kssDD1Y@linutronix.de>

On Tue, Jan 20, 2026 at 11:38:33AM +0100, Sebastian Andrzej Siewior wrote:
> On 2026-01-20 10:21:58 [+0100], Greg Kroah-Hartman wrote:
> > > > Please see patch 0/3 in this series:
> > > > 	https://lore.kernel.org/all/cover.1768751557.git.wen.yang@linux.dev/
> > > 
> > > The reasoning why this is needed is due to PREEMPT_RT. This targets v6.6
> > > and PREEMPT_RT is officially supported upstream since v6.12. For v6.6
> > > you still need the out-of-tree patch. This means not only select the
> > > Kconfig symbol but also a bit futex, ptrace or printk. This queue does
> > > not include the three patches here but has another workaround having
> > > more or less the same effect.
> > > 
> > > If this is needed only for PREEMPT_RT's sake I would suggest to route it
> > > via the stable-rt instead and replace what is currently there.
> > 
> > It's already merged, should this be reverted?  I forgot RT was only for
> > 6.12 and newer, sorry.
> 
> Jakub doesn't seem to be thrilled about this backport and I don't see a
> requirement for it. Based on this yes, please revert it.
> 
> If Wen wants this still to happen he should either provide better
> reasoning why this is needed based on the latest stable v6.6 as-is or
> ask stable-rt team to take this instead the current workaround.

Ok, both now reverted, thanks for the review!

greg k-h

  reply	other threads:[~2026-02-04 13:55 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
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 [this message]
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=2026020449-deplete-swoosh-2387@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