linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Friesen <chris.friesen@windriver.com>
To: <linux-rt-users@vger.kernel.org>
Subject: question about rcuc/X tasks
Date: Mon, 12 Dec 2016 16:42:00 -0600	[thread overview]
Message-ID: <584F27B8.2090406@windriver.com> (raw)

Hi,

I'm testing the CentOS 7.3 RT kernel, 3.10.0-514.rt56.420

(I realize this is a heavily-patched kernel, but I'm hoping general information 
will still apply.)

My kernel is booted with "isolcpus=1-15 rcu_nocbs=1-15" as kernel parameters, 
and /dev/cpu_dma_latency is set to 3.  The relevent config options are set as 
follows:

CONFIG_PREEMPT=y
CONFIG_PREEMPT_RT_BASE=y
CONFIG_HAVE_PREEMPT_LAZY=y
CONFIG_PREEMPT_LAZY=y
CONFIG_PREEMPT_RT_FULL=y
CONFIG_RCU_BOOST=y
CONFIG_RCU_KTHREAD_PRIO=2
CONFIG_RCU_BOOST_DELAY=500
CONFIG_RCU_NOCB_CPU=y
CONFIG_RCU_NOCB_CPU_NONE=y

The issue I'm seeing is that when I run cyclictest, ftrace shows rcuc/<cpu> 
running for 5-6 usec quite a few times per second.

Based on the fact that Documentation/kernel-per-CPU-kthreads.txt describes 
CONFIG_RCU_NOCB_CPU_ALL=y as a solution by preventing the rcuc/%u kthreads from 
having any work to do, I had expected that the "rcu_nocbs=1-15" kernel parameter 
would have a similar effect.

Does anyone have any idea what's going on here, and how I can prevent the 
rcuc/<cpu> tasks from waking up?

Thanks,
Chris

             reply	other threads:[~2016-12-12 22:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-12 22:42 Chris Friesen [this message]
2016-12-15 13:47 ` question about rcuc/X tasks 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
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=584F27B8.2090406@windriver.com \
    --to=chris.friesen@windriver.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).