From: Daniel Wagner <wagi@monom.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
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>
Subject: Re: [ANNOUNCE] v5.10-rc2-rt4
Date: Thu, 12 Nov 2020 13:39:02 +0100 [thread overview]
Message-ID: <20201112123902.netkfwzccwrtscdv@beryllium.lan> (raw)
In-Reply-To: <20201110180518.miuxa25j7lnn7f2q@linutronix.de>
On Tue, Nov 10, 2020 at 07:05:18PM +0100, Sebastian Andrzej Siewior wrote:
> On 2020-11-09 15:37:03 [+0100], Daniel Wagner wrote:
> > > I've been staring at the code of signaltest on Friday and I might need
> > > to stare longer to figure out what it does.
> >
> > I hear you. Anyway, I gave the current head a run with lazy preemption
> > disabled as you asked for.
>
> I just sent a few patches your way regarding signaltest. It should help
> you with tracing. I've been playing with it on a juno box and I didn't
> see anything odd. My max value was below 200us. I added a few tracing
> bits. With sched, signal and hrtimer events you should be able to see
> what delays the RT thread. I didn't see anything odd.
With the current version signaltest + your test patch and 'taskset -c1'
the results looks good again, around 230us (running since 2 hours). I've
tested first without taskset and it took about an half hour to hit
350us. So pinning the threads on one CPU fixes it.
I think we change signaltest to use the correct affinity on
default. Also, I see that sigwaittest has some code for it, but it, but
it would be a good idea to set the defaults so that out of the box the
test does the right thing.
I'm sorry about dragging you into this problem.
next prev parent reply other threads:[~2020-11-12 12:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 19:57 Sebastian Andrzej Siewior
2020-11-04 10:38 ` Daniel Wagner
2020-11-04 10:46 ` Sebastian Andrzej Siewior
2020-11-04 11:19 ` Daniel Wagner
2020-11-04 12:47 ` Daniel Wagner
2020-11-04 13:09 ` Sebastian Andrzej Siewior
2020-11-04 16:06 ` Daniel Wagner
2020-11-06 10:54 ` Sebastian Andrzej Siewior
2020-11-06 16:14 ` Daniel Wagner
2020-11-09 12:47 ` Sebastian Andrzej Siewior
2020-11-09 14:37 ` Daniel Wagner
2020-11-09 16:31 ` Sebastian Andrzej Siewior
2020-11-11 18:39 ` Daniel Wagner
2020-11-10 18:05 ` Sebastian Andrzej Siewior
2020-11-12 12:39 ` Daniel Wagner [this message]
2020-11-12 13:54 ` 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=20201112123902.netkfwzccwrtscdv@beryllium.lan \
--to=wagi@monom.org \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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
Powered by JetHome