public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Wen Yang <wen.yang@linux.dev>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6.6 0/3] net: Backlog NAPI threading for PREEMPT_RT
Date: Mon, 19 Jan 2026 01:02:47 +0800	[thread overview]
Message-ID: <2f5f4a18-82b4-4f67-ae98-cdf5b7f8012b@linux.dev> (raw)
In-Reply-To: <cover.1768751557.git.wen.yang@linux.dev>



Sorry, we accidentally wrote 'PATCH 6.1' as' PATCH 6.6 ', please ignore 
this series.
We will resend the correct one, thanks.

--
Best wishes,
Wen


On 1/19/26 00:15, wen.yang@linux.dev wrote:
> From: Wen Yang <wen.yang@linux.dev>
> 
> Backport three upstream commits to fix a warning on PREEMPT_RT kernels
> where raising SOFTIRQ from smp_call_functio triggers WARN_ON_ONCE()
> in do_softirq_post_smp_call_flush().
> 
> The issue occurs when RPS sends IPIs for backlog NAPI, causing softirqs
> from irq context on PREEMPT_RT. The solution implements backlog
> NAPI threads to avoid IPI-triggered softirqs, which is required for
> PREEMPT_RT kernels.
> 
> commit 8fcb76b934da ("net: napi_schedule_rps() cleanup") and
> commit 56364c910691 ("net: Remove conditional threaded-NAPI wakeup based on task state.")
> are prerequisites.
> 
> The remaining dependencies have not been backported, as they modify
> structure definitions in header files and represent optimizations
> rather than bug fixes, including:
> c59647c0dc67 net: add softnet_data.in_net_rx_action
> a1aaee7f8f79 net: make napi_threaded_poll() aware of sd->defer_list
> 87eff2ec57b6 net: optimize napi_threaded_poll() vs RPS/RFS
> 2b0cfa6e4956 net: add generic percpu page_pool allocator
> ...
> 
> Eric Dumazet (1):
>    net: napi_schedule_rps() cleanup
> 
> Sebastian Andrzej Siewior (2):
>    net: Remove conditional threaded-NAPI wakeup based on task state.
>    net: Allow to use SMP threads for backlog NAPI.
> 
>   net/core/dev.c | 162 +++++++++++++++++++++++++++++++++++--------------
>   1 file changed, 118 insertions(+), 44 deletions(-)
> 

      parent reply	other threads:[~2026-01-18 17:02 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
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 ` Wen Yang [this message]

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=2f5f4a18-82b4-4f67-ae98-cdf5b7f8012b@linux.dev \
    --to=wen.yang@linux.dev \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@vger.kernel.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