public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@elte.hu, laijs@cn.fujitsu.com, dipankar@in.ibm.com,
	akpm@linux-foundation.org, mathieu.desnoyers@polymtl.ca,
	josh@joshtriplett.org, niv@us.ibm.com, tglx@linutronix.de,
	peterz@infradead.org, rostedt@goodmis.org,
	Valdis.Kletnieks@vt.edu, dhowells@redhat.com,
	eric.dumazet@gmail.com
Subject: [PATCH RFC tip/core/rcu 0/3] v1 RCU priority boosting
Date: Tue, 28 Sep 2010 17:33:20 -0700	[thread overview]
Message-ID: <20100929003320.GA15904@linux.vnet.ibm.com> (raw)

Hello!

This patch set is the first version of RCU priority boosting, consisting
of the following:

1.	Add RCU priority inversion testing to rcutorture.
2.	Move TINY_RCU grace-period processing from softirq to kthread
	to allow boosting.
3.	Implement RCU priority boosting for TINY_RCU.

This patch has the following shortcomings, and thus is not yet ready for
inclusion:

o	It does not yet include some restructuring of TREE_RCU that
	is required to make boosting practical.

o	It does not yet include boosting for TREE_RCU.

o	Documentation has not yet been updated.  In the meantime, it is
	important to note that the "rcu_kthread" process must have its
	priority set to at least SCHED_FIFO:2, given that rcutorture
	uses SCHED_FIFO:1 to do the testing.  This priority can be set
	using the new RCU_BOOST_PRIO kernel configuration parameter
	or by using the "chrt" command, for example, "chrt -p 2 6".

o	A great deal more testing is required.

o	There are probably quite a few bugs remaining, even in the parts
	done thus far.

							Thanx, Paul

 b/include/linux/init_task.h |    9 +
 b/include/linux/rcupdate.h  |    1 
 b/include/linux/rcutiny.h   |    8 -
 b/include/linux/rcutree.h   |    1 
 b/include/linux/sched.h     |   11 +
 b/init/Kconfig              |   39 ++++++
 b/kernel/rcutiny.c          |   71 +++++++++--
 b/kernel/rcutiny_plugin.h   |   15 +-
 b/kernel/rcutorture.c       |  270 ++++++++++++++++++++++++++++++++++++++++++--
 kernel/rcutiny.c            |   66 ++++------
 kernel/rcutiny_plugin.h     |  206 ++++++++++++++++++++++++++++++++-
 11 files changed, 608 insertions(+), 89 deletions(-)

             reply	other threads:[~2010-09-29  0:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-29  0:33 Paul E. McKenney [this message]
2010-09-29  0:33 ` [PATCH RFC tip/core/rcu 1/3] rcu: add priority-inversion testing to rcutorture Paul E. McKenney
2010-09-29  0:33 ` [PATCH RFC tip/core/rcu 2/3] rcu: move TINY_RCU from softirq to kthread Paul E. McKenney
2010-09-29  0:33 ` [PATCH RFC tip/core/rcu 3/3] rcu: priority boosting for TINY_PREEMPT_RCU 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=20100929003320.GA15904@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=dipankar@in.ibm.com \
    --cc=eric.dumazet@gmail.com \
    --cc=josh@joshtriplett.org \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=mingo@elte.hu \
    --cc=niv@us.ibm.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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