public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Theodore Tso <tytso@mit.edu>,
	Christoph Hellwig <hch@infradead.org>,
	linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: New ext4 patchset 2.6.26-rc8-ext4-1
Date: Sun, 6 Jul 2008 05:58:23 -0400	[thread overview]
Message-ID: <20080706095823.GA21109@infradead.org> (raw)
In-Reply-To: <20080706024115.GH20240@mit.edu>

On Sat, Jul 05, 2008 at 10:41:15PM -0400, Theodore Tso wrote:
> On Sat, Jul 05, 2008 at 01:50:47PM -0400, Christoph Hellwig wrote:
> > 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.
> 
> Looking back at the mailing list history, yes, we did.  I think the
> reason why we didn't was Andrew had expressed a vague wish that the
> ext4 and xfs developers would get together and try to hash out a
> common layer that all filesystems could work with.  But given that
> nothing has happened in the many months since that discussion, you're
> absolutely right.
> 
> I've reworked the vfs generic patch in the patch series to be much
> smaller --- mainly what's left is simply exporting some mpage
> interfaces that would be needed by ext4.  I trust this is much more to
> your liking?

Yes, this is much better.  But please also add kerneldoc comments for
the newly exported functions.


  reply	other threads:[~2008-07-06  9:58 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
2008-07-06  2:41   ` Theodore Tso
2008-07-06  9:58     ` Christoph Hellwig [this message]
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=20080706095823.GA21109@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