From: Chris Mason <clmason@fusionio.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Jan Kara <jack@suse.cz>,
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>
Subject: Re: [PATCH RFC 0/2] skiplists for range indexes
Date: Sat, 4 May 2013 07:11:51 -0400 [thread overview]
Message-ID: <20130504111151.5844.74450@localhost.localdomain> (raw)
In-Reply-To: <20130504032536.GD19978@dastard>
Quoting Dave Chinner (2013-05-03 23:25:36)
>
> I've got two cases I care about. The first is the buffer cache
> indexes which have a 1000:1 read:modify ratio and I'd really like the
> lookups to be lockless. The other case is the extent tree, where we
> do lots of inserts when the extent tree is first read, and after
> than it's typically 2 lookups for every insert/remove. Having one
> tree that works for both would be handy...
Ok, we're in a similar boat then. I'll finish off some of the API and
test the pure RCU side harder.
For the extent tree, are you doing a lot of merging once things are in
the tree? I'm not planning on doing pure-rcu for items that get merged
quiet yet.
Also, I'm using unsigned longs right now. My guess is we'll both want
u64s, which means I have to do an i_size_read/write trick in a few
spots.
-chris
next prev parent reply other threads:[~2013-05-04 11:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 2:02 [PATCH RFC 0/2] skiplists for range indexes Chris Mason
2013-05-03 2:06 ` [PATCH RFC 1/2] core skiplist code Chris Mason
2013-05-03 2:10 ` [PATCH RFC 2/2] skiplists for the IOMMU Chris Mason
2013-05-03 9:19 ` [PATCH RFC 0/2] skiplists for range indexes Jan Kara
2013-05-03 10:45 ` Chris Mason
2013-05-04 3:25 ` Dave Chinner
2013-05-04 11:11 ` Chris Mason [this message]
2013-05-05 7:33 ` Dave Chinner
2013-05-05 14:38 ` Chris Mason
2013-05-05 22:44 ` Dave Chinner
2013-05-06 11:28 ` [BULK] " Chris Mason
2013-05-07 2:12 ` Dave Chinner
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=20130504111151.5844.74450@localhost.localdomain \
--to=clmason@fusionio.com \
--cc=David.Woodhouse@intel.com \
--cc=bo.li.liu@oracle.com \
--cc=david@fromorbit.com \
--cc=dchinner@redhat.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).