From: Andrew Morton <akpm@linux-foundation.org>
To: Nick Piggin <npiggin@suse.de>
Cc: Linux Filesystems <linux-fsdevel@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [rfc][patch 0/3] a faster buffered write deadlock fix?
Date: Fri, 9 Feb 2007 00:41:01 -0800 [thread overview]
Message-ID: <20070209004101.3e4a88fc.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070208105437.26443.35653.sendpatchset@linux.site>
On Thu, 8 Feb 2007 14:07:15 +0100 (CET) Nick Piggin <npiggin@suse.de> wrote:
> So I have finally finished a first slightly-working draft of my new aops
> op (perform_write) proposal. I would be interested to hear comments about
> it. Most of my issues and concerns are in the patch headers themselves,
> so reply to them.
>
> The patches are against my latest buffered-write-fix patchset.
What happened with Linus's proposal to instantiate the page as pinned,
non-uptodate, unlocked and in pagecache while we poke the user address?
next prev parent reply other threads:[~2007-02-09 8:41 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 13:07 [rfc][patch 0/3] a faster buffered write deadlock fix? Nick Piggin
2007-02-08 13:07 ` [patch 1/3] fs: add an iovec iterator Nick Piggin
2007-02-08 19:49 ` Christoph Hellwig
2007-02-09 1:46 ` Nick Piggin
2007-02-09 2:03 ` Nate Diller
2007-02-09 3:31 ` Nick Piggin
2007-02-09 17:28 ` Zach Brown
2007-03-09 10:40 ` Christoph Hellwig
2007-02-08 23:04 ` Mark Fasheh
2007-02-08 13:07 ` [patch 2/3] fs: introduce perform_write aop Nick Piggin
2007-03-09 10:39 ` Christoph Hellwig
2007-03-09 12:52 ` Nick Piggin
2007-03-09 22:01 ` Anton Altaparmakov
2007-03-09 23:33 ` Mark Fasheh
2007-03-10 9:25 ` Christoph Hellwig
2007-03-12 2:13 ` Mark Fasheh
2007-03-14 13:30 ` Nick Piggin
2007-03-14 15:17 ` Christoph Hellwig
2007-02-08 13:07 ` [patch 3/3] ext2: use " Nick Piggin
2007-02-08 14:47 ` Dmitriy Monakhov
2007-02-09 19:14 ` Andrew Morton
2007-02-09 19:45 ` Andrew Morton
2007-02-10 1:34 ` Nick Piggin
2007-02-10 1:50 ` Andrew Morton
2007-02-09 0:38 ` [rfc][patch 0/3] a faster buffered write deadlock fix? Mark Fasheh
2007-02-09 2:04 ` Nick Piggin
2007-02-09 8:41 ` Andrew Morton [this message]
2007-02-09 9:54 ` Nick Piggin
2007-02-09 10:09 ` Andrew Morton
2007-02-09 10:32 ` Nick Piggin
2007-02-09 10:52 ` Andrew Morton
2007-02-09 11:31 ` Nick Piggin
2007-02-09 11:46 ` Andrew Morton
2007-02-09 12:11 ` 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=20070209004101.3e4a88fc.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=torvalds@linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).