linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mathieu.desnoyers@polymtl.ca, mingo@elte.hu,
	akpm@linux-foundation.org, hch@infradead.org, mmlnx@us.ibm.com,
	dipankar@in.ibm.com, dsmith@redhat.com, rostedt@goodmis.org,
	adrian.bunk@movial.fi, a.p.zijlstra@chello.nl, ego@in.ibm.com,
	niv@us.ibm.com, dvhltc@us.ibm.com, rusty@au1.ibm.com,
	jkenisto@linux.vnet.ibm.com, oleg@tv-sign.ru,
	jamesclhuang@yahoo.com
Subject: [PATCH 0/5] call_rcu_sched() series
Date: Sun, 13 Apr 2008 20:58:48 -0700	[thread overview]
Message-ID: <20080414035848.GA30005@linux.vnet.ibm.com> (raw)

This series adds call_rcu_sched(), applies some fixes to RCU Classic,
adds rcu_barrier_sched(), updates rcutorture, and updates the RCU
documentation.

             reply	other threads:[~2008-04-14  3:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-14  3:58 Paul E. McKenney [this message]
2008-04-14  4:00 ` [PATCH 1/5] Add call_rcu_sched() Paul E. McKenney
2008-04-14  4:01 ` [PATCH 2/5] Add memory barriers and comments to rcu_check_callbacks() Paul E. McKenney
2008-04-14  4:02 ` [PATCH 3/5] Add rcu_barrier_sched() and rcu_barrier_bh() Paul E. McKenney
2008-04-14  4:03 ` [PATCH 4/5] Add call_rcu_sched() and friends to rcutorture Paul E. McKenney
2008-04-14  4:04 ` [PATCH 5/5] 1Q08 RCU doc update, add call_rcu_sched() Paul E. McKenney
2008-04-15  1:33 ` [PATCH 0/5] call_rcu_sched() series Andrew Morton
2008-04-15  1:45   ` Andrew Morton
2008-04-15  1:48     ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2008-04-22  0:44 Paul E. McKenney
2008-04-22  0:45 ` Paul E. McKenney
2008-04-22  0:48 ` Paul E. McKenney
2008-04-22  0:51   ` 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=20080414035848.GA30005@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=adrian.bunk@movial.fi \
    --cc=akpm@linux-foundation.org \
    --cc=dipankar@in.ibm.com \
    --cc=dsmith@redhat.com \
    --cc=dvhltc@us.ibm.com \
    --cc=ego@in.ibm.com \
    --cc=hch@infradead.org \
    --cc=jamesclhuang@yahoo.com \
    --cc=jkenisto@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=mingo@elte.hu \
    --cc=mmlnx@us.ibm.com \
    --cc=niv@us.ibm.com \
    --cc=oleg@tv-sign.ru \
    --cc=rostedt@goodmis.org \
    --cc=rusty@au1.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).