From: Vladimir Saveliev <vs@namesys.com>
To: Valdis.Kletnieks@vt.edu
Cc: "Artem B. Bityuckiy" <dedekind@yandex.ru>,
Hans Reiser <reiser@namesys.com>,
reiserfs-list@namesys.com
Subject: Re: Reiser4 + seekdir()
Date: Thu, 30 Jun 2005 20:26:33 +0400 [thread overview]
Message-ID: <1120148793.3441.82.camel@tribesman.namesys.com> (raw)
In-Reply-To: <200506291811.j5TIBtLo023155@turing-police.cc.vt.edu>
On Wed, 2005-06-29 at 22:11, Valdis.Kletnieks@vt.edu wrote:
> On Wed, 29 Jun 2005 14:22:05 +0400, Vladimir Saveliev said:
>
> > Existence of various plugins assumes that user is able to choose
> > whatever is suitable for him. Or create his own plugin if none of
> > existing ones satisfies him.
> > If user cares a lot about using telldir/seekdir he is supposed to choose
> > SEEKABLE_HASHED_DIR_PLUGIN_ID.
>
> Is that "the user", or "the person building the kernel"?
>
User.
In theory, I think, it is supposed to be like that:
user designes his application. He has some requirements to directories
he stores data in. If he is reading reiserfs mailing lists he should be
aware of reiser4 plugins and implement his application so that if
reiser4 is available - he chooses for his directory a plugin with
properties which match his requirements more.
So far, I think you can choose directory plugin on mkfs time.
next prev parent reply other threads:[~2005-06-30 16:26 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
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 [this message]
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=1120148793.3441.82.camel@tribesman.namesys.com \
--to=vs@namesys.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=dedekind@yandex.ru \
--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.