From: Andreas Dilger <adilger@turbolabs.com>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Ext2 directory index, updated
Date: Thu, 1 Nov 2001 22:04:45 -0700 [thread overview]
Message-ID: <20011101220445.U16554@lynx.no> (raw)
In-Reply-To: <E15zV86-0000o4-00@starship.berlin>
In-Reply-To: <E15zV86-0000o4-00@starship.berlin>; from phillips@bonn-fries.net on Fri, Nov 02, 2001 at 04:36:25AM +0100
On Nov 02, 2001 04:36 +0100, Daniel Phillips wrote:
> I ran it through some basic tests, up to half a million files/directory,
> without problems. There are still a few minor warts to clean up, including
> still not having settled on a final-final hash function, although it looks
> likely that it's going to end up being dx_hack_hash, with a more respectable
> name.
Out of curiosity, does the blkdev-in-pagecache change make the indexed-dir
code simpler? You should just be able to do bread() for a directory
block and it will work, because the "buffer" is actually backed by the
page cache.
Cheers, Andreas
--
Andreas Dilger
http://sourceforge.net/projects/ext2resize/
http://www-mddsp.enel.ucalgary.ca/People/adilger/
next prev parent reply other threads:[~2001-11-02 5:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-02 3:36 Ext2 directory index, updated Daniel Phillips
2001-11-02 5:04 ` Andreas Dilger [this message]
2001-11-04 2:28 Daniel Phillips
2001-11-04 2:44 ` Daniel Phillips
2001-11-04 22:09 ` Christian Laursen
2001-11-04 22:24 ` Daniel Phillips
2001-11-04 22:54 ` Christian Laursen
2001-11-04 23:01 ` Daniel Phillips
2001-11-04 23:09 ` Gábor Lénárt
2001-11-05 22:10 ` Andreas Dilger
2001-11-06 0:38 ` Daniel Phillips
2001-11-05 1:43 ` Daniel Phillips
2001-11-05 7:48 ` Ville Herva
2001-11-05 9:53 ` Daniel Phillips
2001-11-05 22:59 ` Christian Laursen
2001-11-05 23:13 ` Daniel Phillips
2001-11-05 23:45 ` Andreas Dilger
2001-11-08 7:21 ` Christian Laursen
2002-03-04 11:03 Ext2 Directory Index, updated Daniel Phillips
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=20011101220445.U16554@lynx.no \
--to=adilger@turbolabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.net \
/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;
as well as URLs for NNTP newsgroup(s).