From: Christoph Hellwig <hch@infradead.org>
To: Nick Piggin <npiggin@suse.de>
Cc: Mark Fasheh <mark.fasheh@oracle.com>,
Linux Filesystems <linux-fsdevel@vger.kernel.org>
Subject: Re: 2.6.21-rc6 new aops patchset
Date: Tue, 17 Apr 2007 10:33:23 +0100 [thread overview]
Message-ID: <20070417093323.GA4328@infradead.org> (raw)
In-Reply-To: <20070417055944.GA1057@wotan.suse.de>
On Tue, Apr 17, 2007 at 07:59:44AM +0200, Nick Piggin wrote:
> I'll possibly omit the perform_write stuff in the first -mm merge, so
> that we can get the basics reviewed and working, and exercise the
> write_begin/write_end paths well first.
I agree. One thing that should be done for the merge is getting rid
of ->prepare_write and ->commit_write. Historic data show that if
we start a partial transition it will take ages to finish it. In addition
to that the backwards compatibility code in this case is rather big and
very ugly, and we'd be better off without it.
next prev parent reply other threads:[~2007-04-17 9:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-12 4:48 2.6.21-rc6 new aops patchset Nick Piggin
2007-04-12 16:37 ` Badari Pulavarty
2007-04-12 23:25 ` Nick Piggin
2007-04-13 16:42 ` Badari Pulavarty
2007-04-14 0:52 ` Nick Piggin
2007-04-17 18:41 ` Badari Pulavarty
2007-04-18 5:04 ` Nick Piggin
2007-04-12 17:05 ` Miklos Szeredi
2007-04-12 23:41 ` Nick Piggin
2007-04-12 17:27 ` Mark Fasheh
2007-04-12 23:45 ` Nick Piggin
2007-04-17 0:19 ` Mark Fasheh
2007-04-17 5:59 ` Nick Piggin
2007-04-17 9:33 ` Christoph Hellwig [this message]
2007-04-17 9:47 ` Nick Piggin
2007-04-17 9:58 ` Christoph Hellwig
2007-04-17 11:18 ` Nick Piggin
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=20070417093323.GA4328@infradead.org \
--to=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mark.fasheh@oracle.com \
--cc=npiggin@suse.de \
/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