From: Alex Tomas <alex@clusterfs.com>
To: linux-ext4@vger.kernel.org
Cc: <linux-kernel@vger.kernel.org>, alex@clusterfs.com
Subject: [RFC] delayed allocation for ext4
Date: Fri, 22 Dec 2006 23:20:08 +0300 [thread overview]
Message-ID: <m37iwjwumf.fsf@bzzz.home.net> (raw)
Good day,
probably the previous set of patches (including mballoc/lg)
is too large. so, I reworked delayed allocation a bit so
that it can be used on top of regular balloc, though it
still can be used with extents-enabled files only.
this time series contains just 3 patches:
- booked-page-flag.patch
adds PG_booked bit to page->flags. it's used in delayed
allocation to mark space is already reserved for page
(including possible metadata)
- ext4-block-reservation.patch
this is scalable free space management. every time we
delay allocation of some page, a space (including metadata)
should be reserved
- ext4-delayed-allocation.patch
delayed allocation itself, enabled by "delalloc" mount option.
extents support is also required. currently it works only
with blocksize=pagesize.
all the patches can be used in ftp://ftp.clusterfs.com/pub/people/alex/2.6.20-rc1/
the series passed basic tests like dd/dbench/fsx.
any comments/questions are very welcome.
thanks, Alex
next reply other threads:[~2006-12-22 21:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-22 20:20 Alex Tomas [this message]
2006-12-22 20:23 ` [RFC] booked-page-flag.patch Alex Tomas
2006-12-22 20:25 ` [RFC] ext4-block-reservation.patch Alex Tomas
2006-12-23 22:40 ` Andrew Morton
2006-12-23 22:47 ` Alex Tomas
2006-12-22 20:28 ` [RFC] ext4-delayed-allocation.patch Alex Tomas
2006-12-23 22:59 ` Andrew Morton
2007-01-12 14:45 ` Valerie Clement
2007-01-12 14:52 ` Alex Tomas
2006-12-23 3:31 ` [RFC] delayed allocation for ext4 David Chinner
2006-12-23 9:27 ` Christoph Hellwig
2006-12-23 19:15 ` Alex Tomas
2006-12-29 2:50 ` David Chinner
2006-12-23 19:09 ` Alex Tomas
2006-12-29 2:52 ` David Chinner
2006-12-29 4:56 ` Alex Tomas
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=m37iwjwumf.fsf@bzzz.home.net \
--to=alex@clusterfs.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).