From: Joe Seigh <jseigh_02@xemaps.com>
To: linux-kernel@vger.kernel.org
Subject: Yet another lock-free reader/writer lock
Date: Wed, 30 Nov 2005 20:40:29 -0500 [thread overview]
Message-ID: <dmlk6k$6tt$1@sea.gmane.org> (raw)
I have another lock-free algorithm on my FOSS project site
http://atomic-ptr-plus.sourceforge.net/
It's the rcpc (reference counted proxy collector) package.
It uses double wide compare and swap, load reserved/store conditional,
or single wide compare and swap where the former aren't available,
e.g. 64 bit sparc. Which pretty much makes it portable to practically
anything in any environment, kernel or user space.
One caveat. It's probably not safe to use the single wide compare and
swap for 32 bit words if there's a possibility that a read lock will be
held long enough for a 30 bit counter to wrap. But it's probably safe if
the reader does not preempt.
It's ported to 32 bit x86 (linux) and 32 bit ppc (OSX) which is the
only development platforms I have access to. I may port it back to
win32 where I did the initial prototype (it's a vc++ vs. gcc port).
--
Joe Seigh
reply other threads:[~2005-12-01 1:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='dmlk6k$6tt$1@sea.gmane.org' \
--to=jseigh_02@xemaps.com \
--cc=linux-kernel@vger.kernel.org \
/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