From: Clark Williams <clrkwllms@kernel.org>
To: Wen Yang <wen.yang@linux.dev>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>,
linux-rt-devel@lists.linux.dev
Subject: Re: [PATCH 6.6-rt 0/5] net: Backport backlog-NAPI threads to resolve PREEMPT_RT softirq warning in SMP flush
Date: Mon, 19 Oct 2026 12:40:48 -0500 [thread overview]
Message-ID: <atZWIBciePyeMnWa@demetrius> (raw)
In-Reply-To: <b957b12e-f272-4dbf-a308-c6b61bcb3d66@linux.dev>
On Tue, Oct 20, 2026 at 01:18:06AM +0800, Wen Yang wrote:
>
>
> Hi,
>
> Thanks for pushing the rc, and for giving it time to soak before release.
> On your question about the v6.1 series - you're right, it is larger:
> 15 patches. That is mostly because 6.1.y does not carry the ten NAPI/RPS/
> defer_list prerequisites from v6.4-v6.9 that v6.6 already has, so they have
> to come along:
> 10 prerequisite NAPI/RPS/defer_list patches
> 4 the backlog-NAPI changes (the same set as the v6.6 series)
> 1 revert of the RT defer_work workaround
>
> Only one of the 14 upstream patches needed a change beyond context: patch 06
> keeps raise_softirq_irqoff() instead of __raise_softirq_irqoff(), since
> 6.1-rt already carries 533824e6a0fb and the 2023 upstream text predates it.
> The other 13 are line-for-line identical, and patch 13's five hand-placed
> hunks are context only.
>
> The code is unchanged since I posted it, so there is nothing new to send;
> please feel free to apply and test the series as posted.
>
> https://lore.kernel.org/all/cover.1791912669.git.wen.yang@linux.dev/
>
>
> Thanks,
> Wen
>
Meh, 15 patches doesn't suck. I'll try and get to that tonight or
tomorrow and see if we can have both v6.6-rt-next and v6.1-rt-next
soaking.
Clark
--
The United States Coast Guard
Ruining Natural Selection since 1790
next prev parent reply other threads:[~2026-10-19 17:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 18:15 [PATCH 6.6-rt 0/5] net: Backport backlog-NAPI threads to resolve PREEMPT_RT softirq warning in SMP flush wen.yang
2026-10-18 18:15 ` [PATCH 6.6-rt 1/5] Revert "net: Avoid the IPI to free the" wen.yang
2026-10-18 18:15 ` [PATCH 6.6-rt 2/5] net: Remove conditional threaded-NAPI wakeup based on task state wen.yang
2026-10-18 18:15 ` [PATCH 6.6-rt 3/5] net: Allow to use SMP threads for backlog NAPI wen.yang
2026-10-18 18:15 ` [PATCH 6.6-rt 4/5] net: Use backlog-NAPI to clean up the defer_list wen.yang
2026-10-18 18:15 ` [PATCH 6.6-rt 5/5] net: Rename rps_lock to backlog_lock wen.yang
2026-10-19 13:20 ` [PATCH 6.6-rt 0/5] net: Backport backlog-NAPI threads to resolve PREEMPT_RT softirq warning in SMP flush Clark Williams
2026-10-19 17:18 ` Wen Yang
2026-10-19 17:40 ` Clark Williams [this message]
2026-10-19 18:50 ` Clark Williams
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=atZWIBciePyeMnWa@demetrius \
--to=clrkwllms@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=linux-rt-devel@lists.linux.dev \
--cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.