From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Andreas Dilger <adilger@sun.com>, Theodore Tso <tytso@mit.edu>,
Mingming Cao <cmm@us.ibm.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Should we enabling mballoc by default ?
Date: Wed, 9 Jan 2008 23:39:06 +0530 [thread overview]
Message-ID: <20080109180906.GB8259@skywalker> (raw)
Hi,
mballoc currently causes fragmentation of small size files. The
behaviour can be observed by running parallel dd on ext4 file system. A
sample test case can be found here.
http://www.radian.org/~kvaneesh/ext4/mballoc-frag/fragmentation-analysis
This is because for small size request/file mballoc uses group prealloc
space. That means if you have singe cpu and multiple threads doing
parallel io to the file the block request are served from the same
prealloc space. This results in the fragmentation observed above. (Group
prealloc space is per cpu )
This problem should go away with delayed allocation because the write
out happens with multiple blocks and mballoc places then close together
even though they get served by the same group prealloc space.
Considering that we don't have delalloc yet, i guess we should push
mballoc to 2.6.25 with default disabled and O_DIRECT type workloads can
enabled then via mount option.
-aneesh
reply other threads:[~2008-01-09 18:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080109180906.GB8259@skywalker \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=adilger@sun.com \
--cc=cmm@us.ibm.com \
--cc=linux-ext4@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox