From: Jan Kiszka <jan.kiszka@siemens.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Valentin Schneider <vschneid@redhat.com>,
linux-rt-users@vger.kernel.org, linux-kernel@vger.kernel.org,
kprateek.nayak@amd.com, Thomas Gleixner <tglx@linutronix.de>,
Juri Lelli <juri.lelli@redhat.com>,
Clark Williams <williams@redhat.com>,
"Luis Claudio R. Goncalves" <lgoncalv@redhat.com>,
Andreas Ziegler <ziegler.andreas@siemens.com>,
Felix Moessbauer <felix.moessbauer@siemens.com>,
Florian Bezdeka <florian.bezdeka@siemens.com>
Subject: Re: [RT BUG] Stall caused by eventpoll, rwlocks and CFS bandwidth controller
Date: Wed, 9 Apr 2025 15:41:50 +0200 [thread overview]
Message-ID: <be4fa21d-0b96-45de-ac5e-bdb54bee335e@siemens.com> (raw)
In-Reply-To: <20250409132149.rFrzBCrP@linutronix.de>
On 09.04.25 15:21, Sebastian Andrzej Siewior wrote:
> On 2025-04-09 08:41:44 [+0200], Jan Kiszka wrote:
>> We are hunting for quite some time sporadic lock-ups or RT systems,
>> first only in the field (sigh), now finally also in the lab. Those have
>> a fairly high overlap with what was described here. Our baselines so
>> far: 6.1-rt, Debian and vanilla. We are currently preparing experiments
>> with latest mainline.
>>
>> While this thread remained silent afterwards, we have found [1][2][3] as
>> apparently related. But this means we are still with this RT bug, even
>> in latest 6.15-rc1?
>
> Not sure the commits are related. The problem here is that RW locks are
> not really real time friendly. Frederick had a simple fix to it
> https://lore.kernel.org/all/20210825132754.GA895675@lothringen/
>
> but yeah. The alternative, which I didn't look into, would be to replace
> the reader side with RCU so we would just have the writer lock. That
> mean we need to RW lock because of performance…
>
We know that epoll is not a good idea for RT programs. However, our
problem is that already non-RT programs manage to lock up an RT-enabled
system.
We are currently collecting more data to show what we are seeing, plus
will try out the latest patches on the latest kernels.
Jan
--
Siemens AG, Foundational Technologies
Linux Expert Center
next prev parent reply other threads:[~2025-04-09 13:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 15:07 Valentin Schneider
2025-04-09 6:41 ` Jan Kiszka
2025-04-09 9:29 ` K Prateek Nayak
2025-04-09 12:13 ` Aaron Lu
2025-04-09 13:44 ` Jan Kiszka
2025-04-14 14:50 ` K Prateek Nayak
2025-04-14 15:05 ` Sebastian Andrzej Siewior
2025-04-14 15:18 ` K Prateek Nayak
2025-04-15 5:35 ` Jan Kiszka
2025-04-15 6:23 ` Sebastian Andrzej Siewior
2025-04-15 6:54 ` Jan Kiszka
2025-04-15 8:00 ` Sebastian Andrzej Siewior
2025-04-15 10:23 ` Jan Kiszka
2025-04-14 16:21 ` K Prateek Nayak
2025-04-09 13:21 ` Sebastian Andrzej Siewior
2025-04-09 13:41 ` Jan Kiszka [this message]
2025-04-09 13:52 ` Jan Kiszka
2025-04-09 13:57 ` Sebastian Andrzej Siewior
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=be4fa21d-0b96-45de-ac5e-bdb54bee335e@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=bigeasy@linutronix.de \
--cc=felix.moessbauer@siemens.com \
--cc=florian.bezdeka@siemens.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=lgoncalv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=vschneid@redhat.com \
--cc=williams@redhat.com \
--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
all inboxes | Powered by JetHome®