public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Seigh <jseigh_02@xemaps.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Userspace RCU+rtth hack (was Re: [patch 3/3] radix-tree: RCU lockless readside)
Date: Sat, 24 Jun 2006 11:55:29 -0400	[thread overview]
Message-ID: <e7jn3c$rsf$1@sea.gmane.org> (raw)
In-Reply-To: <20060624102024.GA27865@wotan.suse.de>

Nick Piggin wrote:
> On Thu, Jun 22, 2006 at 01:25:53PM -0700, Paul E. McKenney wrote:
> 
> 
>>I have a few user-mode implementations myself, but the lawyers won't
>>let me release them.  :-(
> 
> 
> I imagine they're quite a bit faster than my quick hack, too ;)
> 
> 

I did a number of implementations trying out a number of different strategies.
Yes, they're quite a bit faster and scale better than lock based solutions in
most cases.  They used to be on my atomic-ptr-plus sourceforge project page.
The issue is patents I think.  The RCU patents aren't in any patent pools
for use by open source.  The only thing I think you can do is apply for what
are known as blocking patents for any improvements on RCU.  But you'd have to
sell the patent to recover your patent costs and who would have money for that
do you think, the EFF or a patent troll?

I'm guessing that if lock-free synchronization comes to userspace it will be in
the form of a licensed library that you have to pay for.  There's two out there
already based on Maged Michael's hazard pointers.  One from Intel here
http://www.intel.com/cd/software/products/asmo-na/eng/272688.htm
and one from here http://www.pss-ab.com/

--
Joe Seigh


  reply	other threads:[~2006-06-24 15:52 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-20 14:48 [patch 0/3] 2.6.17 radix-tree: updates and lockless Nick Piggin
2006-06-20 14:48 ` [patch 1/3] radix-tree: direct data Nick Piggin
2006-06-20 14:48 ` [patch 2/3] radix-tree: small Nick Piggin
2006-06-20 14:48 ` [patch 3/3] radix-tree: RCU lockless readside Nick Piggin
2006-06-22  1:49   ` Paul E. McKenney
2006-06-22 15:45     ` Nick Piggin
2006-06-22 16:30       ` Paul E. McKenney
     [not found]         ` <20060622165551.GB23109@wotan.suse.de>
     [not found]           ` <20060622174057.GF1295@us.ibm.com>
2006-06-22 18:11             ` Nick Piggin
2006-06-23  7:09               ` Andrew Morton
2006-06-23  8:03                 ` Nick Piggin
2006-06-23  8:39                 ` Nick Piggin
2006-06-23  8:41                   ` Nick Piggin
2006-06-22 18:23             ` Userspace RCU+rtth hack (was Re: [patch 3/3] radix-tree: RCU lockless readside) Nick Piggin
2006-06-22 20:25               ` Paul E. McKenney
2006-06-24 10:20                 ` Nick Piggin
2006-06-24 15:55                   ` Joe Seigh [this message]
2006-06-20 22:08 ` [patch 0/3] 2.6.17 radix-tree: updates and lockless Benjamin Herrenschmidt
2006-06-20 22:35 ` Andrew Morton
2006-06-20 23:09   ` Benjamin Herrenschmidt
2006-06-20 23:30     ` Andrew Morton
2006-06-20 23:50       ` Benjamin Herrenschmidt
2006-06-21  0:34         ` Christoph Lameter
2006-06-21  0:47           ` Benjamin Herrenschmidt
2006-06-21  1:07             ` Christoph Lameter
2006-06-21  1:33               ` Benjamin Herrenschmidt

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='e7jn3c$rsf$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