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: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
	David Woodhouse <David.Woodhouse@intel.com>,
	"dchinner@redhat.com" <dchinner@redhat.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: Mon, 3 Jun 2013 09:50:47 -0400	[thread overview]
Message-ID: <20130603135047.GB3288@Krystal> (raw)
In-Reply-To: <20130603130706.4088.90651@localhost.localdomain>

* Chris Mason (clmason@fusionio.com) wrote:
> Quoting Mathieu Desnoyers (2013-06-03 08:46:01)
> > > Hi Mathieu,
> > > 
> > > One problem here is that XFS wants to allow duplicate keys in the tree.
> > > This is possible with some modifications to the skiplist code, but I'm
> > > not sure if it fits into your description above.
> > 
> > Are those segments that completely overlap, or partially overlap ?
> 
> I believe completely overlap.  On the skiplist side I'll make it
> possible for either one.

A complete segment overlap is conceptually the same as having duplicate
segments, which makes it easy to handle in my Judy implementation: the
nodes returned by a key lookup are a linked RCU hlist. So when a segment
match is found for a key, iterating on the linked list of duplicate
segments should achieve the intended goal.

Partial overlap can be trickier. There might be extra overhead and
complexity required to support those, so I'll wait until this becomes
really needed before trying to figure out how to support them in Judy.

Thanks,

Mathieu

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

  reply	other threads:[~2013-06-03 13:50 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 [this message]
2013-06-04 11:54     ` Dave Chinner
2013-06-04 14:21       ` Chris Mason
2013-06-04 18:57         ` Mathieu Desnoyers
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=20130603135047.GB3288@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).