Linux real-time development
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: wen.yang@linux.dev, Clark Williams <clrkwllms@kernel.org>,
	linux-rt-devel@lists.linux.dev
Cc: Steven Rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH v6.1-rt 00/15] net: Backport backlog-NAPI threads to resolve PREEMPT_RT softirq warning in SMP flush
Date: Wed, 14 Oct 2026 17:11:37 +0200	[thread overview]
Message-ID: <20261014151137.-fFJKa4D@linutronix.de> (raw)
In-Reply-To: <20261014150853.f8I2fNx0@linutronix.de>

-net folks and lkml
+ linux-rt-devel@lists.linux.dev

On 2026-10-14 17:08:55 [+0200], To wen.yang@linux.dev wrote:
> Please keep the networking folks out of the loop. This is a backport
> request which goes entirely via the RT-queue.
> 
> On 2026-10-14 01:58:34 [+0800], wen.yang@linux.dev wrote:
> > From: Wen Yang <wen.yang@linux.dev>
> > 
> > *** Overview ***
> > Backport the backlog-NAPI smpboot-thread mechanism and its prerequisite
> > NAPI/RPS/defer_list work from upstream (v6.4 - v6.9) to v6.1-rt-next.
> > 
> > *** Problem ***
> > On PREEMPT_RT, RPS steers packets to a remote CPU's backlog by sending an
> > IPI. The IPI handler (rps_trigger_softirq) calls ____napi_schedule(), which
> > raises NET_RX_SOFTIRQ. do_softirq_post_smp_call_flush() then sees a softirq
> > pending that was not pending before the flush, and NET_RX_SOFTIRQ is not
> > masked by SCHED_SOFTIRQ_MASK, so it fires:
> 
> I was about to point out that v6.1-RT should have duct tape for this but
> from reading 1/15 is see that this duct is not complete and is missing
> RPS. Indeed.
> 
> A backport of what is merged is my preference, too. However, we should
> get v6.6-rt fixed first then v6.1-rt. Otherwise users upgrading from
> v6.1 to v6.6 will have this case broken.
> 
> Clark, any objections here from your side?
> 
Sebastian

       reply	other threads:[~2026-10-14 15:11 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   ` Sebastian Andrzej Siewior [this message]
     [not found]   ` <atDWZDywit4ilzJ8@demetrius>
2026-10-15 13:38     ` [PATCH v6.1-rt 00/15] net: Backport backlog-NAPI threads to resolve PREEMPT_RT softirq warning in SMP flush Sebastian Andrzej Siewior
2026-10-16 18:16       ` Wen Yang
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=20261014151137.-fFJKa4D@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=clrkwllms@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox