public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: Josh Triplett <josh@joshtriplett.org>,
	Jon Bernard <jbernard@debian.org>, Jan Blunck <jblunck@suse.de>,
	Pierre Habouzit <madcoder@debian.org>,
	Steven Munroe <munroesj@linux.vnet.ibm.com>,
	Bert Wesarg <bert.wesarg@googlemail.com>,
	Pierre-Marc Fournier <pierre-marc.fournier@polymtl.ca>,
	ltt-dev@lists.casi.polymtl.ca, rp@svcs.cs.pdx.edu,
	linux-kernel@vger.kernel.org
Subject: Re: [RELEASE] Userspace RCU 0.3.0
Date: Tue, 3 Nov 2009 07:50:28 -0800	[thread overview]
Message-ID: <20091103155028.GC6726@linux.vnet.ibm.com> (raw)
In-Reply-To: <20091103150234.GA20060@Krystal>

On Tue, Nov 03, 2009 at 10:02:34AM -0500, Mathieu Desnoyers wrote:
> Hi everyone,
> 
> I released userspace RCU 0.3.0, which includes a small API change for
> the "deferred work" interface. After discussion with Paul, I decided to
> drop the support for call_rcu() and only provide defer_rcu(), to make
> sure I don't provide an API with the same name as the kernel RCU but
> with different arguments and semantic. It will generate the following
> linker error if used:
> 
> file.c:240: undefined reference to 
>    `__error_call_rcu_not_implemented_please_use_defer_rcu'
> 
> Note that defer_rcu() should *not* be used in RCU read-side C.S.,
> because it calls synchronize_rcu() if the queue is full. This is a major
> distinction from call_rcu(). (note to self: eventually we should add
> some self-check code to detect defer_rcu() nested within RCU read-side
> C.S.).
> 
> I plan to eventually implement a proper call_rcu() within the userspace
> RCU library. It's not, however, a short-term need for me at the moment.

I can tell that we need to get you going on some real-time work.  ;-)

(Sorry, but I really couldn't resist!)

							Thanx, Paul

  reply	other threads:[~2009-11-03 15:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-03 15:02 [RELEASE] Userspace RCU 0.3.0 Mathieu Desnoyers
2009-11-03 15:50 ` Paul E. McKenney [this message]
2009-11-03 16:53   ` Mathieu Desnoyers
2009-11-04  6:23     ` 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=20091103155028.GC6726@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=bert.wesarg@googlemail.com \
    --cc=jbernard@debian.org \
    --cc=jblunck@suse.de \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltt-dev@lists.casi.polymtl.ca \
    --cc=madcoder@debian.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=munroesj@linux.vnet.ibm.com \
    --cc=pierre-marc.fournier@polymtl.ca \
    --cc=rp@svcs.cs.pdx.edu \
    /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