From: "Artem B. Bityuckiy" <dedekind@yandex.ru>
To: Hans Reiser <reiser@namesys.com>
Cc: Vladimir Saveliev <vs@namesys.com>, reiserfs-list@namesys.com
Subject: Re: Reiser4 + seekdir()
Date: Wed, 29 Jun 2005 10:51:04 +0400 [thread overview]
Message-ID: <42C244D8.1070408@yandex.ru> (raw)
In-Reply-To: <42C0588C.7030905@namesys.com>
Hans Reiser wrote:
> thanks Artem. If you are generous enough to help us with those comments
> and renames, I'll take a patch to do it. If you are too busy though,
> vs, can you fix it?
Hans,
I may prepare and send a patch once I've realized what is the purpose
and function of these two direntry plugins.
SEEKABLE_HASHED_DIR_PLUGIN_ID and
The HASHED_DIR_PLUGIN_ID plugin's destination is clear - it is general
purpose plugin which should be used in 99% cases except something
special is needed. The plugin implies the dentries are roughly
alphabetically sorted and go in the same order as stat-data. Fine
SEEKABLE_HASHED_DIR_PLUGIN_ID - dunno, it it the same as the
HASHED_DIR_PLUGIN_ID plugin, but the key assignment algorithm is much
simpler. What's the purpose of this plugin? I understand that it used to
be mostly seekable while the first one was not seekable when the
adjust_dir_pos() feature did not exist. But at the moment, what for is it ?
--
Best Regards,
Artem B. Bityuckiy,
St.-Petersburg, Russia.
next prev parent reply other threads:[~2005-06-29 6:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-27 9:28 Reiser4 + seekdir() Artem B. Bityuckiy
2005-06-27 11:41 ` Vladimir Saveliev
2005-06-27 12:09 ` Artem B. Bityuckiy
2005-06-27 12:39 ` Vladimir Saveliev
2005-06-27 12:57 ` Artem B. Bityuckiy
2005-06-27 13:49 ` Vladimir Saveliev
2005-06-27 13:53 ` Artem B. Bityuckiy
2005-06-27 19:50 ` Hans Reiser
2005-06-29 6:51 ` Artem B. Bityuckiy [this message]
2005-06-29 10:22 ` Vladimir Saveliev
2005-06-29 10:29 ` Artem B. Bityuckiy
2005-06-29 11:48 ` Vladimir Saveliev
2005-06-29 18:11 ` Valdis.Kletnieks
2005-06-30 16:26 ` Vladimir Saveliev
2005-06-27 18:09 ` 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=42C244D8.1070408@yandex.ru \
--to=dedekind@yandex.ru \
--cc=reiser@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.