From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Florian Bezdeka <florian.bezdeka@siemens.com>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
"Ziegler, Andreas" <ziegler.andreas@siemens.com>,
"Kiszka, Jan" <jan.kiszka@siemens.com>,
"MOESSBAUER, Felix" <felix.moessbauer@siemens.com>
Subject: Re: 6.1-rt: NOHZ tick-stop error: local softirq work is pending
Date: Wed, 26 Feb 2025 10:17:52 +0100 [thread overview]
Message-ID: <20250226091752.jCsLqq66@linutronix.de> (raw)
In-Reply-To: <d31ddc467399b53c3f0687db63cb64a3a7c77ca5.camel@siemens.com>
On 2025-02-25 16:16:25 [+0100], Florian Bezdeka wrote:
> > which version is this? I think is is an imported issue. Is v6.1.119-rt45
> > also affected?
>
> This is a typo, right? You mean it is an important issue, no?
No, the version is correct. And I meant "imported" as in we got it from
the stable queue.
> We can see that on
>
> - v6.1.90-rt (Debian -rt kernel)
> - v6.1.120-rt (Debian -rt kernel)
> - v6.1.119-rt45 (So yes, this is also affected)
> - v6.1.120-rt47
But if this is visible on v6.1.90-rt then it is not originating from
what I assumed.
> With PERIODIC you mean CONFIG_HZ_PERIODIC, right?
correct.
> We have CONFIG_NO_HZ_FULL=y set but do net set the nohz_full= cmdline
> parameter, so that we should get CONFIG_NO_HZ_IDLE behavior at the end.
>
> I realized today that the warning is somehow related to our RT tuning.
> Enabling NAPI threading makes the warning go away, even if NAPI threads
> are tuned the same way as ksoftirqd.
NAPI threads? You have RPS enabled by any chance?
Would commit
dad6b97702639 ("net: Allow to use SMP threads for backlog NAPI.")
80d2eefcb4c84 ("net: Use backlog-NAPI to clean up the defer_list.")
help?
> I will have to look into that in more depth.
>
> Thanks for your input Sebastian.
You are welcome.
Sebastian
next prev parent reply other threads:[~2025-02-26 9:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 9:32 6.1-rt: NOHZ tick-stop error: local softirq work is pending Bezdeka, Florian
2025-02-24 11:55 ` Sebastian Andrzej Siewior
2025-02-25 15:16 ` Florian Bezdeka
2025-02-26 9:17 ` Sebastian Andrzej Siewior [this message]
2025-02-26 17:41 ` MOESSBAUER, Felix
2025-02-26 22:23 ` Florian Bezdeka
2025-02-27 13:43 ` Sebastian Andrzej Siewior
2025-02-28 16:28 ` Florian Bezdeka
2025-02-28 16:41 ` Jan Kiszka
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=20250226091752.jCsLqq66@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=felix.moessbauer@siemens.com \
--cc=florian.bezdeka@siemens.com \
--cc=jan.kiszka@siemens.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=ziegler.andreas@siemens.com \
/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