From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Daniel Wagner <wagi@monom.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Clark Williams <williams@redhat.com>
Subject: Re: [ANNOUNCE] v5.9.1-rt19
Date: Tue, 27 Oct 2020 12:06:11 +0100 [thread overview]
Message-ID: <20201027110611.5hvuhsp3sjtcshsl@linutronix.de> (raw)
In-Reply-To: <20201027103411.h5ushvwsrovxls5u@beryllium.lan>
On 2020-10-27 11:34:11 [+0100], Daniel Wagner wrote:
> On Tue, Oct 27, 2020 at 11:28:51AM +0100, Sebastian Andrzej Siewior wrote:
> > Is it running as a RT task?
>
> root@c2d:~/rt-tests# ./pi_stress
> Starting PI Stress Test
> Number of thread groups: 1
> Duration of test run: infinite
> Number of inversions per group: unlimited
> Admin thread SCHED_FIFO priority 4
> 1 groups of 3 threads will be created
> High thread SCHED_FIFO priority 3
> Med thread SCHED_FIFO priority 2
> Low thread SCHED_FIFO priority 1
>
> It says so, let me double check if those task really run with SCHED_FIFO.
urgh. You wrote pi_stress and I read stress-ng. Okay this explains it.
> > Otherwise it looks that if you throw enough non-RT load on the system,
> > RCU can not catch up which does not sound good.
>
> I think this is what Clark tried to tell me. If I understood him
> correctly the test tool is not correct though.
a dummy RCU section might help. But otherwise it is correct :/
Sebastian
prev parent reply other threads:[~2020-10-27 11:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-24 9:18 [ANNOUNCE] v5.9.1-rt19 Sebastian Andrzej Siewior
2020-10-27 9:36 ` Daniel Wagner
2020-10-27 10:00 ` Sebastian Andrzej Siewior
2020-10-27 10:25 ` Daniel Wagner
2020-10-27 10:28 ` Sebastian Andrzej Siewior
2020-10-27 10:34 ` Daniel Wagner
2020-10-27 10:52 ` Daniel Wagner
2020-10-27 11:06 ` Sebastian Andrzej Siewior [this message]
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=20201027110611.5hvuhsp3sjtcshsl@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=wagi@monom.org \
--cc=williams@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.