From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Theodore Tso <tytso@mit.edu>
Cc: cmm@us.ibm.com, sandeen@redhat.com, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: Fix small file fragmentation
Date: Fri, 15 Aug 2008 23:37:45 +0530 [thread overview]
Message-ID: <20080815180745.GE6511@skywalker> (raw)
In-Reply-To: <20080815175243.GD6511@skywalker>
On Fri, Aug 15, 2008 at 11:22:43PM +0530, Aneesh Kumar K.V wrote:
> On Thu, Aug 14, 2008 at 07:18:17PM -0400, Theodore Tso wrote:
> > On Thu, Aug 14, 2008 at 11:14:40PM +0530, Aneesh Kumar K.V wrote:
> > > mballoc small file block allocation use per cpu prealloc
> > > space. Use goal block when searching for the right prealloc
> > > space. Also make sure ext4_da_writepages tries to write
> > > all the pages for small files in single attempt
> >
> > Hi Aneesh, how are you testing your patch? I've created the following
> > shell script:
> >
> > -------------------------------
> > #!/bin/sh
> > #
> > # small-files-frag-test --- test for small files fragmentation
> >
> > DEVICE=/dev/thunk/testbench
> >
> > mke2fs -t ext4dev $DEVICE
> > mount -t ext4dev $DEVICE /mnt
> > tar -C /usr -cf - bin lib | tar -C /mnt -xpf -
> > sync; sleep 5
> > umount $DEVICE
> > e2fsck -nfv -E fragcheck $DEVICE
> > -------------------------------
> >
> > ... and the results show roughly the same amount of fragmentation, and the
> > same pattern. In fact, it's a ltitle worse (30% vs 25%).
> >
> > 37912 inodes used (11.57%)
> > 11468 non-contiguous inodes (30.2%)
> > # of inodes with ind/dind/tind blocks: 0/0/0
> > Extent depth histogram: 32638/5
> > 711894 blocks used (54.31%)
> >
>
>
> I have better results with the below patch on top of the patch i sent.
>
> 21156 inodes used (0.47%)
> 158 non-contiguous inodes (0.7%)
> # of inodes with ind/dind/tind blocks: 4/4/4
> 581216 blocks used (3.24%)
> 0 bad blocks
> 1 large file
>
And the fragmented inodes are all directories for which we don't
use prealloc space
debugfs: ncheck 12
Inode Pathname
12 /bin
debugfs: ncheck 1987
Inode Pathname
1987 /lib
debugfs: ncheck 7657
Inode Pathname
7657 /lib/python2.5
debugfs: ncheck 11602
Inode Pathname
11602 /lib/X11/xserver
debugfs: ncheck 14279
Inode Pathname
14279 /lib/locale
debugfs: ncheck 20615
Inode Pathname
20615 /lib/ooo-2.0/program
debugfs:
-aneesh
next prev parent reply other threads:[~2008-08-15 18:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-14 17:44 [PATCH] ext4: Fix small file fragmentation Aneesh Kumar K.V
2008-08-14 22:16 ` Mingming Cao
[not found] ` <20080814231816.GA13048@mit.edu>
2008-08-15 13:38 ` Theodore Tso
2008-08-15 16:31 ` Aneesh Kumar K.V
2008-08-15 16:33 ` Aneesh Kumar K.V
2008-08-15 17:52 ` Aneesh Kumar K.V
2008-08-15 18:07 ` Aneesh Kumar K.V [this message]
2008-08-15 20:05 ` Theodore Tso
2008-08-16 4:43 ` Aneesh Kumar K.V
2008-08-16 10:43 ` Aneesh Kumar K.V
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=20080815180745.GE6511@skywalker \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--cc=sandeen@redhat.com \
--cc=tytso@mit.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.