[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240709074333.2799005-2-radoslaw.zielonek@gmail.com>
Date: Tue, 9 Jul 2024 09:43:34 +0200
From: Radoslaw Zielonek <radoslaw.zielonek@...il.com>
To: peterz@...radead.org
Cc: akpm@...ux-foundation.org,
ardb@...nel.org,
bigeasy@...utronix.de,
brauner@...nel.org,
bristot@...hat.com,
bsegall@...gle.com,
dietmar.eggemann@....com,
juri.lelli@...hat.com,
kunyu@...china.com,
liam.howlett@...cle.com,
linux-kernel@...r.kernel.org,
mgorman@...e.de,
mingo@...hat.com,
oleg@...hat.com,
radoslaw.zielonek@...il.com,
rostedt@...dmis.org,
syzbot+a941018a091f1a1f9546@...kaller.appspotmail.com,
syzkaller-bugs@...glegroups.com,
tandersen@...flix.com,
vincent.guittot@...aro.org,
vincent.whitchurch@...s.com,
vschneid@...hat.com
Subject: Re: [RFC] Signaling overhead on RT tasks is causing RCU stall
> I'm having trouble parsing this. What overhead becomes high? Is the task
> spending time in-kernel? Because if the task is spending time in-user
> handling all its signals, it should accumulate runtime just fine.
The overhead is in kernel. The RT task is preempted over and over by SIGRETURN.
In my case userspace set posix timer interval to 8ns.
The posix_timer_fn enqueues signal (send_sigqueue).
Then when the signal is dequeued (dequeue_signal) the posix timer is rearmed.
Radoslaw
Powered by blists - more mailing lists