From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Austin Schuh <austin.linux@gmail.com>
Cc: linux-rt-users@vger.kernel.org, Brian Silverman <bsilver16384@gmail.com>
Subject: Re: Extra context switches with signalfd on CONFIG_PREEMPT_RT
Date: Thu, 5 Sep 2019 18:02:51 +0200 [thread overview]
Message-ID: <20190905160251.nhgemb3fadw6swgq@linutronix.de> (raw)
In-Reply-To: <CABsbf=Egk6wqEFPTvf9_UtVze80=b38nPzVOdZk-t=QOcUXCWw@mail.gmail.com>
On 2019-08-29 13:55:27 [-0700], Austin Schuh wrote:
>
> This is still RT, but is pretty inefficient. Any suggestions on what
> might be going wrong before I start digging in?
there is a pi-boost sched_switch with state R->D and then de-boost
switch back. This looks like there is a wakeup while a lock is held
which is required by the task that is woken up.
> Thanks,
> Austin
Sebastian
prev parent reply other threads:[~2019-09-05 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-29 20:55 Extra context switches with signalfd on CONFIG_PREEMPT_RT Austin Schuh
2019-09-05 16:02 ` 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=20190905160251.nhgemb3fadw6swgq@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=austin.linux@gmail.com \
--cc=bsilver16384@gmail.com \
--cc=linux-rt-users@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).