From: Anton Altaparmakov <aia21@cam.ac.uk>
To: Vishal Patil <vishpat@gmail.com>
Cc: Gary Funck <gary@intrepid.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Generic B-tree implementation
Date: Wed, 19 Jul 2006 08:33:14 +0100 [thread overview]
Message-ID: <1153294394.13071.3.camel@imp.csi.cam.ac.uk> (raw)
In-Reply-To: <4745278c0607180822u55ffe5b4g333e2e6457b37d02@mail.gmail.com>
On Tue, 2006-07-18 at 11:22 -0400, Vishal Patil wrote:
> B-trees are good for parellel updates as well. Anyway it would be
> great to have inputs from other folks about how B-trees could help
> inside the kernel (if at all)
B-trees are mostly used in file systems in the kernel. For example NTFS
and HFS (and I think HPFS) use B-trees for various metadata like
directory indexes for example.
But of course your implementation is purely userspace and cannot be used
in the kernel (you use recursion for example...) so I am not sure how
you envisage to help the kernel with your code...
Best regards,
Anton
--
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK
Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net
WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/
next prev parent reply other threads:[~2006-07-19 7:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-18 2:02 Vishal Patil
2006-07-18 2:58 ` Horst von Brand
2006-07-18 3:08 ` Vishal Patil
2006-07-18 3:20 ` Valdis.Kletnieks
2006-07-18 4:27 ` Gary Funck
2006-07-18 13:30 ` Vishal Patil
2006-07-18 15:00 ` Gary Funck
2006-07-18 15:13 ` Bob Copeland
2006-07-18 15:22 ` Vishal Patil
2006-07-19 7:33 ` Anton Altaparmakov [this message]
2006-07-19 13:34 ` Vishal Patil
2006-07-19 16:14 ` Andrea Arcangeli
2006-07-19 16:26 ` Vishal Patil
2006-08-07 2:18 ` Vishal Patil
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=1153294394.13071.3.camel@imp.csi.cam.ac.uk \
--to=aia21@cam.ac.uk \
--cc=gary@intrepid.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vishpat@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®