From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Clark Williams <clark.williams@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] rcu: unify boost and kthread priorities
Date: Wed, 17 Sep 2014 08:09:37 -0700 [thread overview]
Message-ID: <20140917150937.GV4723@linux.vnet.ibm.com> (raw)
In-Reply-To: <20140917081442.60425e2d@sluggy>
On Wed, Sep 17, 2014 at 08:14:42AM -0500, Clark Williams wrote:
> On Tue, 16 Sep 2014 13:41:56 -0700
> "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> wrote:
>
> > On Mon, Sep 15, 2014 at 10:05:24AM -0500, Clark Williams wrote:
> > > Paul,
> > >
> > > Here's the result of our conversation Friday, regarding the per-CPU and
> > > boost priorities:
> > >
> > > Rename CONFIG_RCU_BOOST_PRIO to CONFIG_RCU_KTHREAD_PRIO and use this
> > > value for both the per-CPU kthreads (rcuc/N) and the rcu boosting
> > > threads (rcub/n).
> > >
> > > Also, create the module_parameter rcutree.kthread_prio to be used on
> > > the kernel command line at boot to set a new value
> > > (rcutree.kthread_prio=N).
> > >
> > > Signed-off-by: Clark Williams <clark.williams@gmail.com>
> >
> > Thank you, Clark!
> >
> > I queued this, porting to rcu/dev, which resulted in the following
> > patch. Please check this to make sure it still reflects your intent.
> > In the meantime, I will start testing.
> >
> > Thanx, Paul
>
> Yes, looks right (and you fixed that I didn't have it all under
> RCU_BOOST).
Very good! Early testing looks good, will let you know how it goes.
Thanx, Paul
next prev parent reply other threads:[~2014-09-17 15:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 15:05 [PATCH] rcu: unify boost and kthread priorities Clark Williams
2014-09-16 20:41 ` Paul E. McKenney
2014-09-17 13:14 ` Clark Williams
2014-09-17 15:09 ` Paul E. McKenney [this message]
2014-09-17 16:49 ` Paul Bolle
2014-09-17 17:17 ` Paul E. McKenney
2014-09-17 17:45 ` Paul Bolle
2014-09-17 18:25 ` 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=20140917150937.GV4723@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=clark.williams@gmail.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.