From: Andreas Dilger <adilger@clusterfs.com>
To: Ihar `Philips` Filipau <thephilips@gmail.com>
Cc: "Jörn Engel" <joern@wohnheim.fh-wedel.de>,
"Dave Kleikamp" <shaggy@linux.vnet.ibm.com>,
"Bryan Henderson" <hbryan@us.ibm.com>,
"Josef Sipek" <jsipek@fsl.cs.sunysb.edu>,
avishay <atraeger@cs.sunysb.edu>,
linux-fsdevel@vger.kernel.org
Subject: Re: Allocation strategy - dynamic zone for small files
Date: Tue, 14 Nov 2006 11:23:56 -0700 [thread overview]
Message-ID: <20061114182356.GP6012@schatzie.adilger.int> (raw)
In-Reply-To: <efa6f5910611140541m302201e6t4e84551b75e79611@mail.gmail.com>
On Nov 14, 2006 14:41 +0100, Ihar `Philips` Filipau wrote:
> More I'm thinking about that, more I'm convinced that some sort of
> compromise is required. E.g. file system with 2/more cluster sizes:
> for example 4k for small/medium files, 64+k cluster for large files.
> Files of 100+MB sizes are not that rare anymore (home video/audio
> processing now is affordable as never before). But on other side tiny
> files like e.g. found in /etc or ~/.kde/* are not going to disappear
> anytime soon.
Well, current plan is that new allocator (mballoc + delalloc) from
Alex Tomas will do efficient in-memory allocation of many contiguous
blocks, and extents format will allow efficient on-disk storage of
many contiguous blocks, so benefit of larger cluster size in disk
format is minimal.
Essentially, delaying the disk allocation until a file is large/complete
(delalloc) and then using a buddy allocator in memory to get contiguous
chunks of disk is better than hard 64K+ cluster because it avoids
internal fragmentation and allows much more optimal/efficient placement
than just a factor of 16 reduction in the block count.
Cheers, Andreas
--
Andreas Dilger
Principal Software Engineer
Cluster File Systems, Inc.
next prev parent reply other threads:[~2006-11-14 18:23 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-13 10:37 Allocation strategy - dynamic zone for small files Ihar `Philips` Filipau
2006-11-13 13:56 ` avishay
2006-11-13 17:46 ` Bryan Henderson
2006-11-13 19:38 ` Josef Sipek
2006-11-13 21:12 ` Bryan Henderson
2006-11-13 23:32 ` Ihar `Philips` Filipau
2006-11-13 23:57 ` Andreas Dilger
2006-11-14 2:19 ` Dave Kleikamp
2006-11-14 13:15 ` Jörn Engel
[not found] ` <efa6f5910611140541m302201e6t4e84551b75e79611@mail.gmail.com>
2006-11-14 13:56 ` Jörn Engel
2006-11-14 18:23 ` Andreas Dilger [this message]
2006-11-14 15:19 ` phillip
2006-11-14 18:19 ` Andreas Dilger
2006-11-14 0:15 ` Josef Sipek
2006-11-14 0:59 ` Bryan Henderson
2006-11-14 1:02 ` Theodore Tso
2006-11-14 11:21 ` Al Boldi
2006-11-14 14:25 ` Theodore Tso
2006-11-14 15:43 ` Al Boldi
2006-11-14 15:46 ` Matthew Wilcox
2006-11-14 16:59 ` Al Boldi
2006-11-14 17:27 ` Matthew Wilcox
2006-11-14 17:55 ` Theodore Tso
2006-11-14 18:23 ` Al Boldi
2006-11-14 14:30 ` phillip
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=20061114182356.GP6012@schatzie.adilger.int \
--to=adilger@clusterfs.com \
--cc=atraeger@cs.sunysb.edu \
--cc=hbryan@us.ibm.com \
--cc=joern@wohnheim.fh-wedel.de \
--cc=jsipek@fsl.cs.sunysb.edu \
--cc=linux-fsdevel@vger.kernel.org \
--cc=shaggy@linux.vnet.ibm.com \
--cc=thephilips@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).