From: Luiz Capitulino <lcapitulino@redhat.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, linux-rt-users@vger.kernel.org
Subject: Re: kernel-rt rcuc lock contention problem
Date: Wed, 28 Jan 2015 14:06:14 -0500 [thread overview]
Message-ID: <20150128140614.6d1f2cce@redhat.com> (raw)
In-Reply-To: <20150128190047.GU19109@linux.vnet.ibm.com>
On Wed, 28 Jan 2015 11:00:47 -0800
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com> wrote:
> > > 2. You are letting the rcuc kthreads contend for the worker CPUs.
> > > Pin them to housekeeping CPUs. This applies to both the
> > > host and the guest rcuc kthreads, but especially to the
> > > host rcuc kthreads.
> >
> > I'd love to be able to do this, but the rcuc threads are CPU-bound
> > threads. There's one per CPU and the kernel doesn't allow me to move
> > them around.
>
> Can you build with CONFIG_RCU_BOOST=n? Then you won't have any rcuc
> kthreads.
Oh, really? I will try this right away!
Thanks for your help!
next prev parent reply other threads:[~2015-01-28 20:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 19:14 kernel-rt rcuc lock contention problem Luiz Capitulino
2015-01-27 20:37 ` Paul E. McKenney
2015-01-28 1:55 ` Marcelo Tosatti
2015-01-28 14:18 ` Luiz Capitulino
2015-01-28 18:09 ` Paul E. McKenney
2015-01-28 18:39 ` Luiz Capitulino
2015-01-28 19:00 ` Paul E. McKenney
2015-01-28 19:06 ` Luiz Capitulino [this message]
2015-01-28 18:03 ` Paul E. McKenney
2015-01-28 18:25 ` Marcelo Tosatti
2015-01-28 18:55 ` Paul E. McKenney
2015-01-29 17:06 ` Steven Rostedt
2015-01-29 18:11 ` Paul E. McKenney
2015-01-29 18:13 ` Marcelo Tosatti
2015-01-29 18:36 ` Paul E. McKenney
2015-02-02 18:24 ` Marcelo Tosatti
2015-02-02 20:35 ` Steven Rostedt
2015-02-02 20:46 ` Marcelo Tosatti
2015-02-02 20:55 ` Steven Rostedt
2015-02-02 21:02 ` Marcelo Tosatti
2015-02-03 20:36 ` Steven Rostedt
2015-02-03 20:57 ` Paul E. McKenney
2015-02-03 23:55 ` Marcelo Tosatti
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=20150128140614.6d1f2cce@redhat.com \
--to=lcapitulino@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=paulmck@linux.vnet.ibm.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 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).