From: Chris Mason <mason@suse.com>
To: Jamie Lokier <lk@tantalophile.demon.co.uk>
Cc: Andreas Dilger <adilger@turbolinux.com>,
Linux kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: Maximum files per Directory
Date: Sat, 05 May 2001 12:16:47 -0400 [thread overview]
Message-ID: <476470000.989079407@tiny> (raw)
In-Reply-To: <20010505154920.A4571@pcep-jamie.cern.ch>
On Saturday, May 05, 2001 03:49:20 PM +0200 Jamie Lokier
<lk@tantalophile.demon.co.uk> wrote:
> Chris Mason wrote:
>> > Is there a reason that
>> > reiserfs chose to have "large number of directories" represented by "1"
>> > and not "LINK_MAX+1"?
>>
>> find and a few others consider a link count of 1 to mean there is no link
>> count tracking being done.
>
> Indeed, and thank you for getting this right!
>
> Btw, is it possible to add dirent->d_type information to reiserfs, and
> would there be any performance gain in doing so?
reiserfs doesn't store that information in its directory items right now,
but there are plenty of free bits to do so. It wouldn't be hard to add the
feature, and yes there should be a performance gain.
>
> I have code to add d_type for every other filesystem that can support it
> without additional disk reads, but I couldn't figure out whether
> reiserfs can do it or whether stat() following readdir() is cheap anyway.
stat is actually a little more expensive than ext2, since we have to search
for the inode data in the tree. It is a fast search, but...
-chris
next prev parent reply other threads:[~2001-05-05 16:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-01 20:48 Maximum files per Directory Andreas Rogge
2001-05-01 20:58 ` H. Peter Anvin
2001-05-01 22:57 ` Andreas Dilger
2001-05-04 13:49 ` Chris Mason
2001-05-04 19:15 ` Andreas Dilger
2001-05-04 20:08 ` Chris Mason
2001-05-05 13:49 ` Jamie Lokier
2001-05-05 16:16 ` Chris Mason [this message]
2001-05-01 21:02 ` Alan Cox
2001-05-01 22:03 ` H. Peter Anvin
2001-05-02 10:22 ` Ingo Oeser
2001-05-02 16:13 ` H. Peter Anvin
2001-05-02 13:33 ` Ketil Froyn
2001-05-02 9:21 ` Henning P. Schmiedehausen
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=476470000.989079407@tiny \
--to=mason@suse.com \
--cc=adilger@turbolinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lk@tantalophile.demon.co.uk \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox