All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <compudj@krystal.dyndns.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
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: Userspace RCU 0.2.3
Date: Wed, 14 Oct 2009 22:39:25 -0400	[thread overview]
Message-ID: <20091015023925.GA27959@Krystal> (raw)
In-Reply-To: <20091015000225.GG6763@linux.vnet.ibm.com>

* Paul E. McKenney (paulmck@linux.vnet.ibm.com) wrote:
> On Wed, Oct 14, 2009 at 06:36:57PM -0400, Mathieu Desnoyers wrote:
> > Hi,
> > 
> > I just released lib urcu 0.2.3, which is now using autotools. I also
> > integrated automatic architecture detection for old 386 which lack
> > cmpxchg (using a fall-back if necessary). I also use a lock; addl
> > instead of mfence on x86-32 to support a larger variety of older Intel
> > CPUs.
> 
> !!!
> 
> Is there anyone on these lists other than me who has actually used an
> SMP 80386-based system?

SMP 386, ugh, no. But UP 386 yes (at least me). :)

It will become important as the library gets integrated in
distributions.

> 
> Either way, much appreciated for old time's sake.  The things we used
> to do to avoid the need for cmpxchg!  ;-)

In this case I disable signals and take a mutex around the cmpxchg. It's
really a best effort. Should be fine on UP 386, but not so much on SMP
386, as mixing it with assign/xchg pointer could lead to races. I'm not
sure it's worth trying to support 386 SMP though.

Mathieu


> 
> 							Thanx, Paul
> 
> > The build system detects if NR_futex is available in the system
> > headers. It falls back on a more portable alternative if they are not
> > available.
> > 
> > There are also new configuration modes to ./configure for UP-only
> > systems.
> > 
> > As always, the tarballs are available at http://www.lttng.org/urcu
> > 
> > Mathieu
> > 
> > -- 
> > Mathieu Desnoyers
> > OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68
> 

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

  reply	other threads:[~2009-10-15  2:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-14 22:36 Userspace RCU 0.2.3 Mathieu Desnoyers
2009-10-15  0:02 ` Paul E. McKenney
2009-10-15  2:39   ` Mathieu Desnoyers [this message]
2009-10-15  4:34     ` Paul E. McKenney
2009-10-15  9:00     ` Josh Triplett
2009-10-15 17:40       ` Pierre-Marc Fournier
2009-10-17 17:16         ` Pavel Machek
2009-10-18 22:02           ` [rp] " Mathieu Desnoyers
2009-10-18 22:52             ` Pavel Machek
2009-10-18 23:16               ` [ltt-dev] " Mathieu Desnoyers
2009-10-19 23:59               ` Userspace RCU 0.2.4 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=20091015023925.GA27959@Krystal \
    --to=compudj@krystal.dyndns.org \
    --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=munroesj@linux.vnet.ibm.com \
    --cc=paulmck@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.