From: Christoph Hellwig <hch@infradead.org>
To: Nick Piggin <npiggin@suse.de>
Cc: Christoph Hellwig <hch@infradead.org>,
Mark Fasheh <mark.fasheh@oracle.com>,
Linux Filesystems <linux-fsdevel@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [patch 2/3] fs: introduce perform_write aop
Date: Wed, 14 Mar 2007 15:17:03 +0000 [thread overview]
Message-ID: <20070314151703.GA5428@infradead.org> (raw)
In-Reply-To: <20070314133023.GA5103@wotan.suse.de>
On Wed, Mar 14, 2007 at 02:30:24PM +0100, Nick Piggin wrote:
> So I've tried a different approach - the 2-op API rather than an actor.
>
> perform_write stays around as a higher performance API, but it isn't
> required if the filesystem implements the 2-op API. I've called them
> write_begin/write_end for now.
>
> There are a few upshots to doing this rather than the actor approach.
> First of all, this is what callers expect, they want to write into the
> page directly rather than making an actor.
>
> More importantly, it allows us to implement generic block versions of
> the API which is much more reusable than block_perform_write (which was
> basically useless for anything more than ext2).
Generally thiis look pretty cool. But even if we go with perform_write
as aop for now (which I think is a bad idea aswell, but moving it out
would better be done after all filesystems are converted) these should
just stay callbacks passed to generic_perform_write.
next prev parent reply other threads:[~2007-03-14 15:17 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 [this message]
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
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=20070314151703.GA5428@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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 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.