From: "Fred -- Speed Up --" <speedup@free.fr>
To: reiserfs-list@namesys.com
Subject: Re: Some more questions about Reiser4 ;)
Date: Sat, 10 May 2003 20:57:53 +0200 [thread overview]
Message-ID: <007601c31726$10853fb0$9900a8c0@xpstation> (raw)
In-Reply-To: 3EBD46C1.9080801@namesys.com
> >The reason why I asked this was because I didn't knew that VFS was the
one
> >and only responsible for the path resolving ;)
> >
> That is too strong a statement. VFS delegates parts of the task to us,
> particularly directory lookup.
But VFS wants the directory reading task to return a list of files with
corresponding inodes numbers. Reiser4, in this case, has to check out the
tree and read the directory entries, but what about resolving a simple file
path : does VFS in this case want the files and subdirectory listings of
every directory the path consists in, or does VFS directly ask Reiser4 to
resolve the whole path ?
What does Reiser4 do to improve the path resolving and directory listing
performance ? Do you implement another cache even if the VFS allready got
one ?
> Elena, can you draw a diagram or somehow document the disk layout for
> reiser4. We seem to describe the pieces but not the whole.
That would be a great thing ;)
Thank you for all your previous answers ... M. Reiser ;)
Fred
next prev parent reply other threads:[~2003-05-10 18:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 18:30 Some more questions about Reiser4 ;) Fred -- Speed Up --
2003-05-09 11:29 ` Yury Umanets
2003-05-10 15:32 ` Fred -- Speed Up --
2003-05-10 16:09 ` Yury Umanets
2003-05-10 17:39 ` Fred -- Speed Up --
2003-05-10 18:36 ` Hans Reiser
2003-05-10 18:57 ` Fred -- Speed Up -- [this message]
2003-05-11 16:27 ` Hans Reiser
-- strict thread matches above, loose matches on Subject: below --
2003-05-08 6:23 Fred -- Speed Up --
2003-05-03 21:33 Fred -- Speed Up --
2003-05-10 18:43 ` 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='007601c31726$10853fb0$9900a8c0@xpstation' \
--to=speedup@free.fr \
--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.