From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Linus Torvalds <torvalds@linux-foundation.org>,
linux-fsdevel@vger.kernel.org
Cc: Chris Mason <chris.mason@oracle.com>, Jan Kara <jack@suse.cz>,
"Theodore Ts'o" <tytso@mit.edu>,
Linux Kernel Developers List <linux-kernel@vger.kernel.org>,
Ext4 Developers List <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH RFC] ext3 data=guarded v3
Date: Fri, 17 Apr 2009 04:09:01 +1000 [thread overview]
Message-ID: <200904170409.02222.nickpiggin@yahoo.com.au> (raw)
In-Reply-To: <alpine.LFD.2.00.0904151333020.4042@localhost.localdomain>
On Thursday 16 April 2009 06:35:23 Linus Torvalds wrote:
>
> On Wed, 15 Apr 2009, Chris Mason wrote:
> >
> > Here is another version of the data=guarded work for ext3. The main
> > difference between this code and yesterday's is the guarded writepage
> > function now sends any newly allocated block through the old data=ordered code.
>
> I'm inclined to apply the first two patches as infrastructure, since they
> seem to make sense regardless of data=ordered. The ability to get a
> callback when IO ends sounds like something that a number of cases might
> find intriguing, and it's obviously how the actual IO has worked
> internally anyway.
>
> Comments?
I think also fscache really should be using proper read completed notifications
rather than hijacking the page lock waitqueue for this.
next prev parent reply other threads:[~2009-04-16 18:09 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 17:22 [PATCH RFC] ext3 data=guarded v3 Chris Mason
2009-04-15 17:22 ` [PATCH 1/3] Export filemap_write_and_wait_range Chris Mason
2009-04-15 17:22 ` [PATCH 2/3] Add block_write_full_page_endio for passing endio handler Chris Mason
2009-04-15 17:22 ` [PATCH 3/3] Add ext3 data=guarded mode Chris Mason
2009-04-16 19:42 ` [PATCH] " Chris Mason
2009-04-17 11:04 ` Mike Galbraith
2009-04-17 18:09 ` Amit Shah
2009-04-17 20:13 ` Theodore Tso
2009-04-18 6:03 ` Amit Shah
2009-04-18 7:28 ` Mike Galbraith
2009-04-19 6:24 ` Amit Shah
2009-04-20 9:07 ` Mike Galbraith
2009-04-20 9:26 ` Jan Kara
2009-04-20 12:15 ` Mike Galbraith
2009-04-20 12:56 ` Amit Shah
2009-04-20 13:06 ` Mike Galbraith
2009-04-20 13:44 ` Jan Kara
2009-04-20 14:18 ` Chris Mason
2009-04-20 14:42 ` Jan Kara
2009-04-20 14:58 ` Chris Mason
2009-04-20 15:50 ` Jan Kara
2009-04-15 19:10 ` [PATCH RFC] ext3 data=guarded v3 Eric Sandeen
2009-04-19 23:26 ` Bojan Smojver
2009-04-15 20:35 ` Linus Torvalds
2009-04-15 21:09 ` Theodore Tso
2009-04-16 8:44 ` Jan Kara
2009-04-16 18:09 ` Nick Piggin [this message]
2009-04-16 11:39 ` Mike Galbraith
2009-04-16 11:40 ` Mike Galbraith
2009-04-16 14:56 ` Chris Mason
2009-04-16 17:12 ` Chris Mason
2009-04-16 18:25 ` Mike Galbraith
2009-04-16 18:37 ` Linus Torvalds
2009-04-16 19:38 ` Chris Mason
2009-04-16 18:00 ` Mike Galbraith
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=200904170409.02222.nickpiggin@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=chris.mason@oracle.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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