From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Ionut Nechita (Wind River)" <ionut.nechita@windriver.com>,
florian.bezdeka@siemens.com
Cc: crwood@redhat.com, namcao@linutronix.de, brauner@kernel.org,
linux-fsdevel@vger.kernel.org, linux-rt-users@vger.kernel.org,
stable@vger.kernel.org, linux-kernel@vger.kernel.org,
frederic@kernel.org, vschneid@redhat.com,
gregkh@linuxfoundation.org, chris.friesen@windriver.com,
viorel-catalin.rapiteanu@windriver.com,
iulian.mocanu@windriver.com
Subject: Re: [REGRESSION] osnoise: "eventpoll: Replace rwlock with spinlock" causes ~50us noise spikes on isolated PREEMPT_RT cores
Date: Sat, 28 Mar 2026 07:00:14 +0100 [thread overview]
Message-ID: <22ffc044-4cc7-468c-b11d-9b838c92e82b@siemens.com> (raw)
In-Reply-To: <20260327183610.594667-1-ionut.nechita@windriver.com>
On 27.03.26 19:36, Ionut Nechita (Wind River) wrote:
> From: Ionut Nechita <ionut.nechita@windriver.com>
>
> On Thu, 2026-03-27 at 08:44 +0100, Florian Bezdeka wrote:
>> A revert alone is not an option as it would bring back [1] and [2]
>> for all LTS releases that did not receive [3].
>
> Florian, Crystal, thanks for the feedback.
>
> I understand the revert concern regarding the CFS throttle deadlock.
> However, I want to clarify that the noise regression on isolated cores
> is a separate issue from the deadlock fixed by [3], and it remains
> unfixed even on linux-next which has [3] merged or not.
>
> I've done extensive testing across multiple kernels to identify the
> exact mechanism. Here are the results.
>
> Tool: eBPF-based osnoise tracer (https://gitlab.com/rt-linux-tools/eosnoise)
> which uses perf_event_open() + epoll on each monitored CPU, combined
> with /proc/interrupts delta measurement.
>
> Setup:
> - Hardware: x86_64, SMT/HT enabled (CPUs 0-63)
I think Crystal already asked: Are you disabling HT then by taking the
the siblings offline for the isolated cores? If not, the measurements
are a bit questionable from an RT perspective.
Jan
--
Siemens AG, Foundational Technologies
Linux Expert Center
next prev parent reply other threads:[~2026-03-28 6:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 14:00 [REGRESSION] osnoise: "eventpoll: Replace rwlock with spinlock" causes ~50µs " Ionut Nechita (Wind River)
2026-03-26 14:31 ` Sebastian Andrzej Siewior
2026-03-26 14:52 ` Greg KH
2026-03-26 16:21 ` Ionut Nechita (Wind River)
2026-03-26 18:12 ` Crystal Wood
2026-03-27 7:44 ` Florian Bezdeka
2026-03-27 18:36 ` [REGRESSION] osnoise: "eventpoll: Replace rwlock with spinlock" causes ~50us " Ionut Nechita (Wind River)
2026-03-27 21:20 ` Crystal Wood
2026-03-28 6:00 ` Jan Kiszka [this message]
2026-04-01 16:58 ` Ionut Nechita (Wind River)
2026-04-02 4:42 ` Nam Cao
2026-04-02 8:59 ` Ionut Nechita (Wind River)
2026-04-02 9:49 ` Tomas Glozar
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=22ffc044-4cc7-468c-b11d-9b838c92e82b@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=brauner@kernel.org \
--cc=chris.friesen@windriver.com \
--cc=crwood@redhat.com \
--cc=florian.bezdeka@siemens.com \
--cc=frederic@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=ionut.nechita@windriver.com \
--cc=iulian.mocanu@windriver.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=namcao@linutronix.de \
--cc=stable@vger.kernel.org \
--cc=viorel-catalin.rapiteanu@windriver.com \
--cc=vschneid@redhat.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
all inboxes | Powered by JetHome®