public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
* Should we enabling mballoc by default ?
@ 2008-01-09 18:09 Aneesh Kumar K.V
  0 siblings, 0 replies; only message in thread
From: Aneesh Kumar K.V @ 2008-01-09 18:09 UTC (permalink / raw)
  To: Andreas Dilger, Theodore Tso, Mingming Cao; +Cc: ext4 development

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

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2008-01-09 18:09 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-01-09 18:09 Should we enabling mballoc by default ? Aneesh Kumar K.V

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox