From: Hans Reiser <reiser@namesys.com>
To: Chris Mason <mason@suse.com>
Cc: Ross Skaliotis <mross@rs-net.org>, reiserfs-list@namesys.com
Subject: Re: Calling stat with millions of files
Date: Tue, 08 Jun 2004 09:58:31 -0700 [thread overview]
Message-ID: <40C5F037.3040807@namesys.com> (raw)
In-Reply-To: <1086713475.10973.125.camel@watt.suse.com>
Chris Mason wrote:
>On Tue, 2004-06-08 at 12:47, Hans Reiser wrote:
>
>
>>really afford to do it just for you, sorry.
>>
>>
>>>You'll get better results with the new block allocator in 2.6.7-rcX-mm,
>>>but in the end the stat information for the file isn't horribly close to
>>>the directory entries, and performance won't be perfect.
>>>
>>>Hans, I thought reiser4 was going to be good at this kind of thing?
>>>
>>>
>>>
>>>
>>what in reiser4 optimizes accesses to hard links to files whose stat
>>data is stored in other directories? Maybe the stat data being stored
>>near other stat data instead of near file bodies will help,. Hmmm.
>>Could be, have to try it to see.
>>
>>
>
>He said above that it creates hard links "when it can", not sure what
>percentage of the time this actually happens.
>
>-chris
>
>
>
>
>
>
Probably reiser4 will indeed do much better at this. Wish I had more
guys working on the debugging.....;-)
next prev parent reply other threads:[~2004-06-08 16:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-07 21:54 Calling stat with millions of files Ross Skaliotis
2004-06-08 10:03 ` Vladimir Saveliev
2004-06-08 12:00 ` Heinz-Josef Claes
2004-06-08 16:28 ` Hans Reiser
2004-06-08 16:38 ` Chris Mason
2004-06-08 16:47 ` Hans Reiser
2004-06-08 16:51 ` Chris Mason
2004-06-08 16:58 ` Hans Reiser [this message]
2004-06-08 17:57 ` Ross Skaliotis
2004-06-08 22:10 ` Hans Reiser
2004-06-08 22:05 ` Carl-Daniel Hailfinger
2004-06-08 18:58 ` Mike Benoit
2004-06-08 20:29 ` Henning Westerholt
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=40C5F037.3040807@namesys.com \
--to=reiser@namesys.com \
--cc=mason@suse.com \
--cc=mross@rs-net.org \
--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.