linux-kernel - Re: filesystem benchmarking fun

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 16 May 2007 12:33:42 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Chris Mason <chris.mason@...cle.com>
Cc:	Chuck Ebbert <cebbert@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: filesystem benchmarking fun

On Wed, 16 May 2007 15:13:39 -0400
Chris Mason <chris.mason@...cle.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.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/