public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <compudj@krystal.dyndns.org>
To: Jon Bernard <jbernard@debian.org>, Jan Blunck <jblunck@suse.de>,
	linux-kernel@vger.kernel.org,
	Pedro Alves <pedro@codesourcery.com>,
	ltt-dev@lists.casi.polymtl.ca,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	pierre-marc.fournier@polymtl.ca
Subject: Userspace RCU API (minor changes)
Date: Fri, 15 Jan 2010 12:23:35 -0500	[thread overview]
Message-ID: <20100115172335.GC30678@Krystal> (raw)

Hi,

I'd like to proceed to a minor API change in the next userspace RCU
release: moving from SIGURCU to SIGRCU for the signal name. This is part
of an effort to standardize the library prefix to "rcu_".  I plan to
add support for backward compatibility, so when we see that SIGURCU is
defined, then we use that value.

Also, I am planning to rename the urcu_init() constructor to rcu_init().
It should only affect the libust tracer, which need to call it
explicitly. Normal users don't have to bother with it, as it's a library
constructor.

Also, the urcu/config.h options are renamed to:

CONFIG_RCU_HAVE_FENCE
CONFIG_RCU_HAVE_FUTEX
CONFIG_RCU_SMP
CONFIG_RCU_COMPAT_ARCH
(moving from URCU -> RCU)

So an updated system installation will keep everything in sync.

I also plan to shuffle the library names a bit, but without breaking
anything. Basically, liburcu will become the "default" version, using
sys_membarrier() when available, and using liburcu-mb as a fallback.

The signal-based liburcu will be renamed from liburcu to liburcu-signal.
People previously using the signal-based "liburcu" will automatically be
moved to the "default" liburcu version.

You might want to have a look at the current git tree head to see if
everything is fine before the release. Given that I change the API
slightly, this will definitely be a 0.4.0.

Feedback is welcome,

Thanks,

Mathieu

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68

             reply	other threads:[~2010-01-15 17:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-15 17:23 Mathieu Desnoyers [this message]
2010-01-30 18:33 ` [RELEASE] Userspace RCU 0.4.0 Mathieu Desnoyers

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=20100115172335.GC30678@Krystal \
    --to=compudj@krystal.dyndns.org \
    --cc=jbernard@debian.org \
    --cc=jblunck@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltt-dev@lists.casi.polymtl.ca \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=pedro@codesourcery.com \
    --cc=pierre-marc.fournier@polymtl.ca \
    /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