From: "Matthias Urlichs" <smurf@noris.de>
To: Hans Reiser <reiser@namesys.com>
Cc: Nikita Danilov <Nikita@Namesys.COM>,
Oleg Drokin <green@namesys.com>,
reiserfs-list@namesys.com
Subject: Re: fsck mode halfway between --fix-fixable and --rebuild-tree ?
Date: Tue, 1 Oct 2002 14:15:09 +0200 [thread overview]
Message-ID: <20021001141508.L32363@noris.de> (raw)
In-Reply-To: <3D998037.8030508@namesys.com>; from reiser@namesys.com on Tue, Oct 01, 2002 at 03:00:07PM +0400
Hi,
Hans Reiser:
> >Actually, B-link trees (B-trees with sibling pointers) don't require any
> >additional io for sibling pointers maintenance. Just draw a picture of
> >what is going on during insertion of new node or node deletion and you
> >will see.
> >
> They have constraints we do not desire. Also, I think they link in only
> one direction. Am I right?
>
Whether you use just a forward-pointing link or also a back-pointing link
(or nothing at all) is up to you. Personally I like sibling and parent
links because it is very easy to walk the tree iteratively (just follow
the "next" or "prev" pointer when you're done with a node). Trees which
only use downward-pointing links need to be walked recursively.
On the other hand, you're a multitasking file system, therefore you need
locking, therefore side pointers won't be of much use to you for anything
(except additional redundancy for error recovery).
--
Matthias Urlichs | noris network AG | http://smurf.noris.de/
next prev parent reply other threads:[~2002-10-01 12:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-28 9:28 Reiserfs/emacs incompatibility/bug ? arthur.chereau
2002-09-29 15:23 ` fsck mode halfway between --fix-fixable and --rebuild-tree ? Matthias Urlichs
2002-09-30 6:18 ` Oleg Drokin
2002-09-30 11:12 ` Hans Reiser
2002-09-30 11:15 ` Oleg Drokin
2002-09-30 11:17 ` Matthias Urlichs
2002-09-30 11:22 ` Oleg Drokin
2002-09-30 13:08 ` Matthias Urlichs
2002-09-30 13:20 ` Hans Reiser
2002-09-30 17:36 ` Matthias Urlichs
2002-09-30 17:56 ` Valdis.Kletnieks
2002-10-01 6:37 ` Nikita Danilov
2002-10-01 7:32 ` Matthias Urlichs
2002-10-01 7:44 ` Nikita Danilov
2002-10-01 11:02 ` Hans Reiser
2002-10-01 11:00 ` Hans Reiser
2002-10-01 11:12 ` Nikita Danilov
2002-10-01 12:15 ` Matthias Urlichs [this message]
2002-10-01 18:43 ` Hans Reiser
2002-10-02 8:13 ` Matthias Urlichs
2002-10-02 11:04 ` Vitaly Fertman
2002-10-02 12:21 ` Matthias Urlichs
2002-09-30 15:15 ` Vitaly Fertman
2002-09-30 11:43 ` Vitaly Fertman
2002-09-29 23:54 ` Reiserfs/emacs incompatibility/bug ? Matthias Andree
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=20021001141508.L32363@noris.de \
--to=smurf@noris.de \
--cc=Nikita@Namesys.COM \
--cc=green@namesys.com \
--cc=reiser@namesys.com \
--cc=reiserfs-list@namesys.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.