From: Daniel Phillips <phillips@bonn-fries.net>
To: linux-kernel@vger.kernel.org
Cc: Albert Cranford <ac9410@bellsouth.net>
Subject: Re: [PATCH][CFT] (updated) ext2 directories in pagecache
Date: Mon, 7 May 2001 01:16:27 +0200 [thread overview]
Message-ID: <01050701135600.07657@starship> (raw)
This patch updates ext2_getblk and ext2_bread to use the ERR_PTR style
of error return. As Al Viro pointed out, this is a better way of doing
things for a function returning a pointer. This approach would have
prevented the bug I fixed with the previous patch. 20 20 hindsight,
and I can only plead that I was following the interface of the old
ext2_getblk. But since these functions are only used only by the ext2
directory code - which in turn is the only part of ext2 that is
interested in file data - there was no problem changing the interface.
The patch is at:
http://nl.linux.org/~phillips/htree/dx.pcache-2.4.4-4
This is lightly tested and apparently stable. I wish I could say the
same for kernel 2.4.4 - cache performance sucks horribly.
(Nontechnical evaluation.) So it is probably not a good idea to take
benchmarks too seriously this month. The previous stable kernels,
2.4.2 and 2.4.3, had their problems too, fixable via patching. Maybe
next month...
This patch requires Al Viro's directory-in-page-cache patch to be
applied first, available from:
ftp://ftp.math.psu.edu/pub/viro/ext2-dir-patch-S4.gz
The other flavor of indexing patch, dx.testme..., also does
directory-in-page-cache, using the good old ext2 directory code. This
works fine and is stable, but IMHO Al's patches constitute a pretty
major cleanup.
To apply:
cd source/tree
zcat ext2-dir-patch-S4.gz | patch -p1
cat dx.pcache-2.4.4-4 | patch -p0
To create an indexed directory:
mount /dev/hdxxx /test -o index
mkdir /test/foo
--
Daniel
next reply other threads:[~2001-05-06 23:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-06 23:16 Daniel Phillips [this message]
2001-05-09 21:22 ` [PATCH][CFT] (updated) ext2 directories in pagecache Andreas Dilger
2001-05-11 1:04 ` Daniel Phillips
-- strict thread matches above, loose matches on Subject: below --
2001-05-11 7:10 Andreas Dilger
2001-05-11 7:19 ` Alexander Viro
2001-05-11 16:34 ` Andreas Dilger
2001-05-11 20:20 ` Daniel Phillips
2001-05-12 21:41 ` Andreas Dilger
2001-05-12 22:18 ` Alexander Viro
2001-05-13 2:13 ` Daniel Phillips
2001-05-13 2:34 ` Daniel Phillips
2001-05-14 18:33 ` Andreas Dilger
2001-05-14 19:29 ` Daniel Phillips
2001-05-14 21:50 ` Daniel Phillips
2001-05-16 3:11 ` Daniel Phillips
2001-05-11 13:02 ` Daniel Phillips
2001-05-10 20:53 Andreas Dilger
2001-05-11 1:10 ` Daniel Phillips
2001-05-10 7:21 Andreas Dilger
2001-05-13 22:15 ` Daniel Phillips
2001-05-14 20:04 ` Andreas Dilger
2001-05-14 22:18 ` Daniel Phillips
2001-05-14 22:23 ` Daniel Phillips
2001-05-03 21:10 Daniel Phillips
2001-05-03 22:59 ` Albert Cranford
[not found] <01050303150500.00633@starship>
2001-05-03 1:43 ` Daniel Phillips
2001-04-29 20:35 Daniel Phillips
2001-05-02 3:03 ` Albert Cranford
2001-04-12 16:33 [PATCH][CFT] " Alexander Viro
2001-04-23 22:21 ` [PATCH][CFT] (updated) " Alexander Viro
2001-04-28 18:16 ` Alexander Viro
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=01050701135600.07657@starship \
--to=phillips@bonn-fries.net \
--cc=ac9410@bellsouth.net \
--cc=linux-kernel@vger.kernel.org \
/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