From: Daniel Phillips <phillips@bonn-fries.net>
To: Andreas Dilger <adilger@turbolinux.com>
Cc: Andreas Dilger <adilger@turbolinux.com>,
Alexander Viro <viro@math.psu.edu>,
Linux kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][CFT] (updated) ext2 directories in pagecache
Date: Mon, 14 May 2001 23:50:59 +0200 [thread overview]
Message-ID: <01051423505900.24410@starship> (raw)
In-Reply-To: <200105141833.f4EIXrQs001765@webber.adilger.int>
In-Reply-To: <200105141833.f4EIXrQs001765@webber.adilger.int>
On Monday 14 May 2001 20:33, Andreas Dilger wrote:
> Daniel, you write:
> > Now, if the check routine tells us how much good data it found we
> > could use that to set a limit for the dirent scan, thus keeping the
> > same robustness as the old code but without having all the checks
> > in the inner loop. Or. We could have separate loops for good
> > blocks and bad blocks, it's just a very small amount of code.
>
> Yes, I was thinking about both of those as well. I think the latter
> would be easiest, because we only need to keep a single error bit per
> buffer.
Today's patch has the first part of that fix:
http://nl.linux.org/~phillips/htree/dx.pcache-2.4.4-6
I broke up Al's check_page routine into the page-specific part and the
dirent-specific part, which I call every time a buffer is brought
uptodate in ext2_bread. This is roughly as efficient as Al's
page-oriented check. I could get rid of the code in Al's check_page
that initializes sets the rec_lens of a new dir page to blocksize
because I do that explicitly in ext2_add_entry now. This will make it
a little cleaner.
The next step is to try and incorporate the intelligence about the good
parts of a bad dirent block into the entry lookup code cleanly.
I moved ext2_bread and ext2_append into dir.c because of their
dir-specific nature. (I have some plans for ext2_getblk that have
nothing to do with directories, which is why I'm trying to keep it
generic.)
--
Daniel
next prev parent reply other threads:[~2001-05-14 21:55 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-11 7:10 [PATCH][CFT] (updated) ext2 directories in pagecache 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 [this message]
2001-05-16 3:11 ` Daniel Phillips
2001-05-11 13:02 ` Daniel Phillips
-- strict thread matches above, loose matches on Subject: below --
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-06 23:16 Daniel Phillips
2001-05-09 21:22 ` Andreas Dilger
2001-05-11 1:04 ` 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=01051423505900.24410@starship \
--to=phillips@bonn-fries.net \
--cc=adilger@turbolinux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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