linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Chris Mason <clmason@fusionio.com>
Cc: Dave Chinner <dchinner@redhat.com>,
	Linux FS Devel <linux-fsdevel@vger.kernel.org>,
	David Woodhouse <David.Woodhouse@intel.com>,
	"bo.li.liu@oracle.com" <bo.li.liu@oracle.com>,
	"rp@svcs.cs.pdx.edu" <rp@svcs.cs.pdx.edu>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Lai Jiangshan <laijs@cn.fujitsu.com>,
	Stephen Hemminger <shemminger@vyatta.com>,
	Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [RFC] RCU Judy array with distributed locking for FS extents
Date: Tue, 4 Jun 2013 14:57:17 -0400	[thread overview]
Message-ID: <20130604185717.GA7138@Krystal> (raw)
In-Reply-To: <20130604142132.4088.42487@localhost.localdomain>

* Chris Mason (clmason@fusionio.com) wrote:
[...]
> In terms of comparing the two, I'd rather compare in the kernel so we
> don't have any surprises.  Are you willing to port the judy code in?

I'm in a similar situation as yours on the Judy side: I still need to
clean up the API and extend its documentation (this is why the Judy code
is still in a development branch), and I'd prefer to have the API
stabilized on the userspace RCU side before porting it to the kernel.
Moreover, I see that it might be a good thing to create an API on top of
Judy to handle overlapping and non-overlapping sparse index ranges.
Ideally, I'd like to implement this and test it in user-space before
porting to the kernel.

I'd be very much interested in helping out in porting your skip list
code to Userspace RCU, I think this should be very much straightforward.
By the way, would you be willing to license it under LGPLv2.1 so it
could be integrated within the Userspace RCU code base ?

Thanks,

Mathieu

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com

  reply	other threads:[~2013-06-04 18:57 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-03  5:27 [RFC] RCU Judy array with distributed locking for FS extents Mathieu Desnoyers
2013-06-03 12:40 ` Chris Mason
2013-06-03 12:46   ` Mathieu Desnoyers
2013-06-03 13:07     ` Chris Mason
2013-06-03 13:50       ` Mathieu Desnoyers
2013-06-04 11:54     ` Dave Chinner
2013-06-04 14:21       ` Chris Mason
2013-06-04 18:57         ` Mathieu Desnoyers [this message]
2013-06-05 23:48         ` Dave Chinner
2013-06-12  1:12         ` Mathieu Desnoyers
2013-06-13  1:25           ` Chris Mason
2013-06-16 14:02             ` Liu Bo

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=20130604185717.GA7138@Krystal \
    --to=mathieu.desnoyers@efficios.com \
    --cc=David.Woodhouse@intel.com \
    --cc=bo.li.liu@oracle.com \
    --cc=clmason@fusionio.com \
    --cc=dchinner@redhat.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=rp@svcs.cs.pdx.edu \
    --cc=shemminger@vyatta.com \
    --cc=stern@rowland.harvard.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;
as well as URLs for NNTP newsgroup(s).