From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Chris Friesen <chris.friesen@windriver.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Daniel Bristot de Oliveira <daniel@bristot.me>,
linux-rt-users@vger.kernel.org
Subject: Re: question about rcuc/X tasks
Date: Thu, 15 Dec 2016 15:34:30 -0800 [thread overview]
Message-ID: <20161215233430.GF3924@linux.vnet.ibm.com> (raw)
In-Reply-To: <585317DF.7080502@windriver.com>
On Thu, Dec 15, 2016 at 04:23:27PM -0600, Chris Friesen wrote:
> On 12/15/2016 01:04 PM, Paul E. McKenney wrote:
> >On Thu, Dec 15, 2016 at 09:20:24AM -0600, Chris Friesen wrote:
>
> >>On a related note, I found an old email from Paul suggesting that
> >>the various rcuc/X threads could be affined to the management CPUs
> >>to free up the "realtime" cores, but when I try that it doesn't let
> >>me change affinity. Was that disallowed for technical reasons?
> >>(It's also possible it's something local, in which case I need to go
> >>digging.)
> >
> >The rcuo/X kthreads can be affined, but the rcuc/X kthreads must run on
> >the corresponding CPU for correctness reasons -- they communicate with
> >RCU core using protocols that are only single-CPU-safe. But if you are
> >running NO_HZ_FULL, these kthreads should never run unless your user
> >threads are doing syscalls.
> >
> >So, are they actually running in your setup?
>
> Yes, but I wasn't setting nohz_full. With "rcu_nocb_poll
> isolcpus=1-15 rcu_nocbs=1-15 nohz_full=1-15" I'm not seeing the
> rcuc/X kthreads running.
>
> So in the non-nohz_full case, what are they waking up to do?
> Something timer-related?
Interesting. I need to look into this a bit. I would not expect
that rcuc/X kthreads corresponding to NOCB CPUs to ever wake up.
(They are created by a per-CPU facility that creates a kthread per
CPU no matter what.)
Thanx, Paul
next prev parent reply other threads:[~2016-12-15 23:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-12 22:42 question about rcuc/X tasks Chris Friesen
2016-12-15 13:47 ` Daniel Bristot de Oliveira
2016-12-15 14:07 ` Steven Rostedt
2016-12-15 15:20 ` Chris Friesen
2016-12-15 19:04 ` Paul E. McKenney
2016-12-15 22:23 ` Chris Friesen
2016-12-15 23:34 ` Paul E. McKenney [this message]
2016-12-16 2:43 ` Chris Friesen
2016-12-15 19:01 ` Paul E. McKenney
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=20161215233430.GF3924@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=chris.friesen@windriver.com \
--cc=daniel@bristot.me \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.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).