mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gyutae Bae <gyutae.opensource@navercorp.com>
To: Paolo Abeni <pabeni@redhat.com>, stable@vger.kernel.org
Cc: Thomas Gleixner <tglx@kernel.org>,
	Eric Dumazet <edumazet@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Jason Xing <kerneljasonxing@gmail.com>,
	Peter Zijlstra <peterz@infradead.org>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Minsu Jeon <minsu.jeon@navercorp.com>,
	Jonghyeon Kim <jong-hyeon.kim@navercorp.com>,
	Siwan Kim <siwan.kim@navercorp.com>,
	Gyutae Bae <gyutae.bae@navercorp.com>
Subject: Re: Backport request: Revert "softirq: Let ksoftirqd do its job" (d15121be7485)
Date: Fri, 30 Oct 2026 13:42:28 +0900	[thread overview]
Message-ID: <20261030044228.7815-1-gyutae.opensource@navercorp.com> (raw)
In-Reply-To: <9024faed-854d-411d-96c1-7cefd4d68dc6@redhat.com>

On 10/29/26 09:33, Paolo Abeni wrote:
> IMHO such change should not land to stable lightly. It's a behavioural
> change with subtle side effects. The threaded napi feature is disabled
> by default for the same reason. Also the revert has some soft functional
> dependencies in napi threaded cleanup and improvements landed into v6.4,
> i.e. 6bb218b5a6e3f3c5e2e76faf8fc976f3f6f72496, likely more.

Thanks for taking a look. I understand the concern about changing
behavior in stable kernels.

Gyutae Bae

  reply	other threads:[~2026-10-30  4:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-29  5:42 Gyutae Bae
2026-10-29  8:33 ` Paolo Abeni
2026-10-30  4:42   ` Gyutae Bae [this message]
2026-10-30  6:16   ` Jason Xing
2026-10-30 14:15     ` Greg KH

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=20261030044228.7815-1-gyutae.opensource@navercorp.com \
    --to=gyutae.opensource@navercorp.com \
    --cc=bigeasy@linutronix.de \
    --cc=edumazet@kernel.org \
    --cc=gyutae.bae@navercorp.com \
    --cc=jong-hyeon.kim@navercorp.com \
    --cc=kerneljasonxing@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minsu.jeon@navercorp.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=siwan.kim@navercorp.com \
    --cc=stable@vger.kernel.org \
    --cc=tglx@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
all inboxes | Powered by JetHome®