From: Andrew Morton <akpm@linux-foundation.org>
To: Chris Mason <chris.mason@oracle.com>
Cc: Chuck Ebbert <cebbert@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: filesystem benchmarking fun
Date: Wed, 16 May 2007 12:33:42 -0700 [thread overview]
Message-ID: <20070516123342.714a11d8.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070516191339.GA26766@think.oraclecorp.com>
On Wed, 16 May 2007 15:13:39 -0400
Chris Mason <chris.mason@oracle.com> wrote:
> >
> > If that's still working then the problem will _probably_ be directory
> > writeout. Possibly inodes, but they should be well-laid-out.
> >
> > Were you using dir_index? That might be screwing things up.
>
> Yes, dir_index. A quick test of mkfs.ext3 -O ^dir_index seems to still
> have the problem. Even though the inodes are well laid out, is the
> order they get written sane?
Should be: it uses first-fit.
> Looks like ext3 is just walking a list of
> bh/jh, maybe we can just sort the silly thing?
The IO scheduler is supposed to do that.
But I don't know what's causing this.
next prev parent reply other threads:[~2007-05-16 19:37 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 14:42 Chris Mason
2007-05-16 16:01 ` Chuck Ebbert
2007-05-16 17:11 ` Chris Mason
2007-05-16 18:25 ` Andrew Morton
2007-05-16 19:13 ` Chris Mason
2007-05-16 19:33 ` Andrew Morton [this message]
2007-05-16 19:53 ` Chris Mason
2007-05-16 20:04 ` Andrew Morton
2007-05-16 20:14 ` Chris Mason
2007-05-16 20:37 ` Andrew Morton
2007-05-16 21:02 ` Chris Mason
2007-05-24 17:29 ` Vara Prasad
2007-05-22 16:35 ` Chris Mason
2007-05-22 17:50 ` John Stoffel
2007-05-22 18:12 ` Chris Mason
2007-05-22 18:21 ` Andrew Morton
2007-05-22 18:39 ` Chris Mason
2007-05-22 21:25 ` Matt Mackall
2007-05-25 7:14 ` Jens Axboe
2007-05-16 18:12 ` Jan Engelhardt
2007-05-16 19:12 ` Jeff Garzik
2007-05-16 19:16 ` Jeffrey Hundstad
2007-05-16 19:21 ` Jan Engelhardt
2007-05-18 3:32 ` Eric Sandeen
2007-05-16 19:25 ` Chris Mason
2007-05-16 21:01 Al Boldi
2007-05-17 11:52 Xu CanHao
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=20070516123342.714a11d8.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=cebbert@redhat.com \
--cc=chris.mason@oracle.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
Powered by JetHome