LKML Archive on lore.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, tglx@linuxtronix.de, dipankar@in.ibm.com,
	tytso@us.ibm.com, dvhltc@us.ibm.com, oleg@tv-sign.ru,
	twoerner.k@gmail.com, josh@freedesktop.org,
	billh@gnuppy.monkey.org, nielsen.esben@googlemail.com,
	corbet@lwn.net
Subject: [RFC PATCH -rt 0/2] RCU priority boosting that survives semi-vicious testing
Date: Wed, 24 Jan 2007 18:11:01 -0800	[thread overview]
Message-ID: <20070125021101.GA23428@linux.vnet.ibm.com> (raw)

Hello!

This is an update of the patch at http://lkml.org/lkml/2007/01/15/219.
This series contains (1) the RCU-boost patch itself and (2) some
rcutorture modifications to test it more thoroughly.  This version is
getting quite close.

There is still no OOM tie-in.  As before, dynamic adjustment of the
booster's priority will dynamically adjust the boostees.

						Thanx, Paul

             reply	other threads:[~2007-01-25  2:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-25  2:11 Paul E. McKenney [this message]
2007-01-25  2:14 ` [RFC PATCH -rt 1/2] " Paul E. McKenney
2007-01-25  2:23   ` [RFC PATCH -rt 2/2] RCU priority boosting additions to rcutorture Paul E. McKenney
2007-01-25  8:47     ` Josh Triplett
2007-01-25 18:01       ` Paul E. McKenney
2007-01-25 19:06         ` Josh Triplett
2007-01-26  1:52           ` Paul E. McKenney
2007-01-26  6:29             ` Josh Triplett
2007-01-29  2:11           ` Paul E. McKenney
2007-01-29  6:05             ` Josh Triplett
2007-01-25  9:29   ` [RFC PATCH -rt 1/2] RCU priority boosting that survives semi-vicious testing Josh Triplett
2007-01-25 19:58     ` Paul E. McKenney
2007-01-26  1:47       ` Paul E. McKenney
2007-01-26  6:13         ` Josh Triplett

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=20070125021101.GA23428@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=billh@gnuppy.monkey.org \
    --cc=corbet@lwn.net \
    --cc=dipankar@in.ibm.com \
    --cc=dvhltc@us.ibm.com \
    --cc=josh@freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nielsen.esben@googlemail.com \
    --cc=oleg@tv-sign.ru \
    --cc=tglx@linuxtronix.de \
    --cc=twoerner.k@gmail.com \
    --cc=tytso@us.ibm.com \
    --subject='Re: [RFC PATCH -rt 0/2] RCU priority boosting that survives semi-vicious testing' \
    /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

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).