public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Yusuf Goolamabbas <yusufg@outblaze.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Your ext2 optimisation for readdir+stat
Date: Mon, 20 Aug 2001 22:09:43 +0800	[thread overview]
Message-ID: <20010820220942.A18903@outblaze.com> (raw)


> The patch won't work for the 2.2 kernels or 2.4 ext3, since it
> requires that the directories-in-page-cache change.  It's
> theoretically possible to rewrite the change for the old-style
> ext2/3_find_entry code, but (a) the ext2_find_entry() function before
> it was modified to use the page cache is rather icky, and (b) I don't
> particularly care about 2.2 at this point.
> 
> The only reason why I might try to do this work is if we really want
> this optimization in ext3 before we add support for putting
> directories in the page cache (which isn't going to happen before the
> ext3 1.0 release), but as I said, it would require messing with a
> complicated bit of code, and it's not high on my priority list at the
> moment.

I think it would be great to have this for ext3. Andrew Morton has done
a lot of work to make ext3 very usable for MTA applications.
Postfix/qmail use 'find' either in their control script or whilst
providing queue statistics. Your optimisations would greatly speed these
operations up. I believe tarring directory trees might also get a
speedup and maybe cvs operations

Regards, Yusuf

-- 
Yusuf Goolamabbas
yusufg@outblaze.com

             reply	other threads:[~2001-08-20 13:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-20 14:09 Yusuf Goolamabbas [this message]
     [not found] <20010820042921.14473.qmail@yusufg.portal2.com>
     [not found] ` <20010820082440.C8399@thunk.org>
2001-08-20 18:22   ` Your ext2 optimisation for readdir+stat Theodore Tso

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=20010820220942.A18903@outblaze.com \
    --to=yusufg@outblaze.com \
    --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