From: Joe Thornber <thornber@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: Alasdair G Kergon <agk@redhat.com>
Subject: Re: btree vs. linear seach in device mapper
Date: Mon, 8 Apr 2013 10:56:39 +0100 [thread overview]
Message-ID: <20130408095638.GA21248@debian> (raw)
In-Reply-To: <Pine.LNX.4.64.1304041901170.29240@file.rdu.redhat.com>
On Thu, Apr 04, 2013 at 07:03:45PM -0400, Mikulas Patocka wrote:
>
>
> On Thu, 4 Apr 2013, Joe Thornber wrote:
>
> > On Thu, Apr 04, 2013 at 10:27:02AM -0400, Mikulas Patocka wrote:
> > > BTW. when I see that btree code in dm-table.c, I ask - why doesn't it use
> > > binary search?
> > >
> > > We only append targets at the end when constructing the device, we never
> > > insert or remove them, so we don't need a tree. For these operations
> > > binary search would be as good as btree and it is simpler.
> >
> > I originally expected dm tables to have many, many more entries than
> > they do these days (I remember benchmarking it with 1 million
> > entries). I used a btree to try and be nicer to the cpu cache; the
> > idea being that each btree node could fit into a cache line. Plain
> > binary search would have caused many more cache faults.
> >
> > Given how dm is used these days I wouldn't mind a switch to a binary
> > search.
> >
> > - Joe
>
> I see.
>
> If the btree helps to save a few cachelines and doesn't hurt, we can leave
> it there. If it ever causes some code maintainability difficulties, we can
> switch to a binary search...
Agreed, it's been there for 10 years without issue. There are better
things to spend your time on.
- Joe
prev parent reply other threads:[~2013-04-08 9:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <515599DE.3050104@redhat.com>
[not found] ` <20130404085848.GC24402@stefanha-thinkpad.redhat.com>
[not found] ` <Pine.LNX.4.64.1304040916470.17024@file.rdu.redhat.com>
2013-04-04 14:27 ` btree vs. linear seach in device mapper Mikulas Patocka
2013-04-04 14:43 ` Joe Thornber
2013-04-04 23:03 ` Mikulas Patocka
2013-04-08 9:56 ` Joe Thornber [this message]
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=20130408095638.GA21248@debian \
--to=thornber@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.