All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wen Yang <wen.yang@linux.dev>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Clark Williams <clrkwllms@kernel.org>
Cc: Steven Rostedt <rostedt@goodmis.org>, linux-rt-devel@lists.linux.dev
Subject: Re: [PATCH v6.1-rt 00/15] net: Backport backlog-NAPI threads to resolve PREEMPT_RT softirq warning in SMP flush
Date: Sat, 17 Oct 2026 02:16:02 +0800	[thread overview]
Message-ID: <2c3a8c0f-3820-4531-b179-b2656a7d3c7e@linux.dev> (raw)
In-Reply-To: <20261015133811.PtBdJYyx@linutronix.de>



On 10/15/26 21:38, Sebastian Andrzej Siewior wrote:
> - NET + proper list
> 
> On 2026-10-15 08:34:28 [-0500], Clark Williams wrote:
>> I don't have a fundamental objection to the backport and agree we should
>> do v6.6-rt first, then move that back to v6.1-rt.
> 
> Okay.
> 
>> So it sounds like we need to pull in the RPS code first?
> 
> Yes. Wen, do you mind preparing a series for v6.6-RT?
> 

Hi Sebastian, Clark,

Thanks for the feedback.
Agreed, v6.6-rt should be fixed first to avoid reintroducing the issue
when users upgrade from v6.1-rt. Regarding the RPS prerequisites, I will
check which upstream changes are already present in v6.6-rt and identify
the remaining dependencies for the backlog-NAPI threads and defer_list
cleanup. I will prepare and test a series for v6.6-RT soon.

Thanks,
Wen

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

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1791912669.git.wen.yang@linux.dev>
     [not found] ` <20261014150853.f8I2fNx0@linutronix.de>
2026-10-14 15:11   ` [PATCH v6.1-rt 00/15] net: Backport backlog-NAPI threads to resolve PREEMPT_RT softirq warning in SMP flush Sebastian Andrzej Siewior
     [not found]   ` <atDWZDywit4ilzJ8@demetrius>
2026-10-15 13:38     ` Sebastian Andrzej Siewior
2026-10-16 18:16       ` Wen Yang [this message]
2026-10-16 19:00         ` 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=2c3a8c0f-3820-4531-b179-b2656a7d3c7e@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 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.