Linux real-time development
 help / color / mirror / Atom feed
From: Wen Yang <wen.yang@linux.dev>
To: Clark Williams <clrkwllms@kernel.org>
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: Thu, 22 Oct 2026 00:30:22 +0800	[thread overview]
Message-ID: <7f5046fd-f38e-4966-a616-0c8d95833eed@linux.dev> (raw)
In-Reply-To: <atZmgh0uq6sTdWTc@demetrius>



On 10/20/26 02:50, Clark Williams wrote:
> On Mon, Oct 19, 2026 at 12:40:48PM -0500, Clark Williams wrote:
>> 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
>> -- 
> 
> Wen,
> 
> I was reading back through the threads and the previous series and am
> confused as to whether your 15-patch series has all the RPS code that's
> required. I seem to recall Sebastian indicating that the original
> v6.1-rt patchset needed some extra RPS bits?
> 
> Clark
> 

Hi Clark,

Thanks for checking, and sorry for confusion.

My understanding is that Sebastian's comment referred to the existing
RT defer_work workaround, which covers deferred freeing but not RPS.

After rechecking against the upstream code, I haven't found an 
additional RPS prerequisite needed for this series.

Sebastian, could you please check whether this addresses your earlier
concern about RPS coverage? I'd appreciate any pointers to prerequisites
I may have missed.

Thanks,
Wen

  reply	other threads:[~2026-10-21 16:30 UTC|newest]

Thread overview: 13+ 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
2026-10-19 18:50       ` Clark Williams
2026-10-21 16:30         ` Wen Yang [this message]
2026-10-21 20:28           ` Clark Williams
2026-10-22  8:01             ` Sebastian Andrzej Siewior

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=7f5046fd-f38e-4966-a616-0c8d95833eed@linux.dev \
    --to=wen.yang@linux.dev \
    --cc=bigeasy@linutronix.de \
    --cc=clrkwllms@kernel.org \
    --cc=linux-rt-devel@lists.linux.dev \
    --cc=rostedt@goodmis.org \
    /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