From: Eric Sandeen <sandeen@redhat.com>
To: Andreas Dilger <adilger@clusterfs.com>
Cc: Avantika Mathur <mathur@linux.vnet.ibm.com>, linux-ext4@vger.kernel.org
Subject: Re: Ext4 devel interlock meeting minutes (October 1, 2007)
Date: Tue, 02 Oct 2007 09:23:38 -0500 [thread overview]
Message-ID: <4702546A.1050802@redhat.com> (raw)
In-Reply-To: <20071002055831.GH5702@schatzie.adilger.int>
Andreas Dilger wrote:
> On Oct 01, 2007 15:10 -0700, Avantika Mathur wrote:
>> Delayed Allocation:
>> - There has been an lkml thread about these patches.
>> - We have and approach that works for ext4, implemented at the vfs
>> level, but unless we can prove it can work for other filesystems, it
>> will not be accepted.
>> - Christoph Hellwig has commented that these patches will not work for
>> XFS.
>
> Hmm, but I thought that Christoph also agreed that it would be OK to
> get the ext4 delalloc code merged separately, so long as it doesn't
> need big/any changes to the VFS to implement it. It might be that the
> ext4 and XFS code is different enough that they cannot share the
> delayed allocation code.
IIRC there is only one change to the VFS, a test for buffer_delay() in
__block_write_full_page(). XFS is the only current caller of
set_buffer_delay, and XFS does not even use the block_write_full_page path.
The rest was a huge chunk dropped into mpage.c, but not interfering with
anything else.
So, I don't see any conflict.
-Eric
next prev parent reply other threads:[~2007-10-02 14:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-01 22:10 Ext4 devel interlock meeting minutes (October 1, 2007) Avantika Mathur
2007-10-02 5:58 ` Andreas Dilger
2007-10-02 14:23 ` Eric Sandeen [this message]
2007-10-02 9:24 ` Valerie Clement
2007-10-02 11:36 ` Aneesh Kumar K.V
2007-10-02 14:12 ` Andreas Dilger
2007-10-02 18:10 ` Aneesh Kumar K.V
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=4702546A.1050802@redhat.com \
--to=sandeen@redhat.com \
--cc=adilger@clusterfs.com \
--cc=linux-ext4@vger.kernel.org \
--cc=mathur@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.