From: Christoph Hellwig <hch@infradead.org>
To: David Chinner <dgc@sgi.com>
Cc: Alex Tomas <alex@clusterfs.com>,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] delayed allocation for ext4
Date: Sat, 23 Dec 2006 09:27:18 +0000 [thread overview]
Message-ID: <20061223092718.GA26276@infradead.org> (raw)
In-Reply-To: <20061223033123.GL44411608@melbourne.sgi.com>
On Sat, Dec 23, 2006 at 02:31:23PM +1100, David Chinner wrote:
> > - ext4-delayed-allocation.patch
> > delayed allocation itself, enabled by "delalloc" mount option.
> > extents support is also required. currently it works only
> > with blocksize=pagesize.
>
> Ah, that's why you can get away with a page flag - you've ignored
> the partial page delay state problem. Any plans to use the
> existing method in the future so we will be able to use ext4 delalloc
> on machines with a page size larger than 4k?
I think fixing this up for blocksize < pagesize is an absolute requirement
to get things merged. We don't need more filesystems that are crippled
on half of our platforms.
Note that recording delayed alloc state at a page granularity in addition
to just the buffer heads has a lot of advantages aswell and would help
xfs, too. But I think it makes a lot more sense to record it as a radix
tree tag to speed up the gang lookups for delalloc conversion.
next prev parent reply other threads:[~2006-12-23 9:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-22 20:20 [RFC] delayed allocation for ext4 Alex Tomas
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 [this message]
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=20061223092718.GA26276@infradead.org \
--to=hch@infradead.org \
--cc=alex@clusterfs.com \
--cc=dgc@sgi.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).