From: Nikita Danilov <nikita@clusterfs.com>
To: Nate Diller <ndiller@namesys.com>
Cc: reiserfs-list@namesys.com, Vladimir Saveliev <vs@namesys.com>
Subject: Re: Novice question
Date: Thu, 07 Apr 2005 02:07:41 +0400 [thread overview]
Message-ID: <m18y3vimoi.fsf@clusterfs.com> (raw)
In-Reply-To: <42545769.8000804@namesys.com> (Nate Diller's message of "Wed, 06 Apr 2005 14:40:57 -0700")
Nate Diller <ndiller@namesys.com> writes:
>
> Node: Implemented as a file system block, the basic unit for the tree.
> On x86, a node is 4KiB in size, however, there is no restriction on
> it's size (is that true?), and there is no design restriction
In current implementation node is bound to of the same size as page in
the page cache on the underlying platform, but this is not design
restriction.
>
[...]
>
> Key: Every item has exactly one key, which is it's non-unique
> identifier within the tree. When the semantic layer wants to store
Every _unit_ has exactly one key. Item spans key-range covered by its
units.
> data, it asks the key assignment plugin for a key, and then invokes
there is no key assignment plugin... yet. Key assignment is hard-coded.
[...]
>
> Directory: Directory objects map a set of strings (names) to their
> corresponding objectID(?). The hash plugin is specified per directory
Hash plugin is specified for one particular instance of directory
plugin: hashed-directory plugin. Other directory plugins may use
completely different indexing techniques.
Nikita.
next prev parent reply other threads:[~2005-04-06 22:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-06 21:40 Novice question Nate Diller
2005-04-06 22:07 ` Nikita Danilov [this message]
2005-04-07 7:12 ` Vladimir Saveliev
-- strict thread matches above, loose matches on Subject: below --
2005-04-06 13:19 Jagannadha Bhattu
2005-04-06 14:58 ` Vladimir Saveliev
2005-04-07 5:49 ` Hans Reiser
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=m18y3vimoi.fsf@clusterfs.com \
--to=nikita@clusterfs.com \
--cc=ndiller@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=vs@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.