From: Christoph Hellwig <hch@infradead.org>
To: Theodore Ts'o <tytso@mit.edu>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: New ext4 patchset 2.6.26-rc8-ext4-1
Date: Sat, 5 Jul 2008 13:50:47 -0400 [thread overview]
Message-ID: <20080705175047.GA11243@infradead.org> (raw)
In-Reply-To: <E1KFBPc-0006yI-Gx@closure.thunk.org>
On Sat, Jul 05, 2008 at 01:19:04PM -0400, Theodore Ts'o wrote:
> Alex Tomas (2):
> * vfs: add basic delayed allocation support
> * ext4: Add basic delayed allocation support
Strong NACK. For one thing the code added to mpage.c doesn't belong
there. It's far inferior to the existing delalloc code we already have
and that could be made generic easily, or the next generation code
developed by Chris mason. It's an ext4-specific hack and doesn't belong
into common code. I'm pretty sure we agreed on not having it in
common code long ago.
Also the code still deals with the !buffer_mapped and no buffers on page
cases all over which isn't needed anymore with ->page_mkwrite implemented.
Similarly the !get_block case in mpage_da_writepages doesn't make any
sense - it's never used and if people would want to use
generic_writepages they could trivially just call it directly.
And please fix up the indentation of the new buffer_delay checks in
fs/buffer.c, the && belongs on the end of the previous line, and the
second line of the conditional should not be indented the same amount
as the code inside the conditional block.
next prev parent reply other threads:[~2008-07-05 17:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-05 17:19 New ext4 patchset 2.6.26-rc8-ext4-1 Theodore Ts'o
2008-07-05 17:50 ` Christoph Hellwig [this message]
2008-07-06 2:41 ` Theodore Tso
2008-07-06 9:58 ` Christoph Hellwig
2008-07-08 19:53 ` Jan Kara
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=20080705175047.GA11243@infradead.org \
--to=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@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