From: Andreas Dilger <adilger@clusterfs.com>
To: Marc-Christian Petersen <mcp@linux-systeme.de>
Cc: Daniel Phillips <phillips@arcor.de>, linux-kernel@vger.kernel.org
Subject: Re: htree directory indexing 2.4.18-2 BUG with highmem and also high i/o
Date: Wed, 10 Jul 2002 18:49:33 -0600 [thread overview]
Message-ID: <20020711004933.GD1045@clusterfs.com> (raw)
In-Reply-To: <200207110103.37380.mcp@linux-systeme.de>
On Jul 11, 2002 01:03 +0200, Marc-Christian Petersen wrote:
> > On Wednesday 10 July 2002 23:01, Andreas Dilger wrote:
> > > The ext2 htree patch probably needs to add a "kmap()" and "kunmap()"
> > > in the function that reads a page and scans the directory for the
> > > name it is looking for. I can't be any more specific than this
> > > right now since I only have the ext3 version of this patch, and it
> > > does not have page-cache based directories (it is still using the
> > > buffer cache).
>
> Say, where can i find those patch for ext3? I've searched a long time and
> never found it?! :|
The most up-to-date version is in the ext3 CVS tree at sourceforge:
http://sourceforge.net/projects/gkernel/
the ext3 package therein has "features-branch" on which the ext3 htree
patch has already been applied (along with other ext3 fixes). If you
only want the ext3 htree patch, you can also get it from the "lustre"
sourceforge project at "lustre/extN/htree-ext3-2.4.18.diff".
Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/
prev parent reply other threads:[~2002-07-11 0:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-09 21:33 htree directory indexing 2.4.18-2 BUG with highmem and also high i/o Marc-Christian Petersen
2002-07-10 21:01 ` Andreas Dilger
2002-07-10 22:46 ` Daniel Phillips
2002-07-10 23:03 ` Marc-Christian Petersen
2002-07-11 0:49 ` Andreas Dilger [this message]
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=20020711004933.GD1045@clusterfs.com \
--to=adilger@clusterfs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcp@linux-systeme.de \
--cc=phillips@arcor.de \
/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