From: David Howells <dhowells@redhat.com>
To: nickpiggin@yahoo.com.au, hch@infradead.org
Cc: dhowells@redhat.com, nfsv4@linux-nfs.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/4] CacheFiles: Use the ->write() file op rather than a special kernel aop
Date: Fri, 03 Apr 2009 10:51:56 +0100 [thread overview]
Message-ID: <9759.1238752316@redhat.com> (raw)
In-Reply-To: <20090403094138.9510.80681.stgit@warthog.procyon.org.uk>
David Howells <dhowells@redhat.com> wrote:
> This reverts the patch:
>
> CacheFiles: Add a hook to write a single page of data to an inode
>
> Add an address space operation to write one single page of data to an
> inode at a page-aligned location (thus permitting the implementation to
> be highly optimised). The data source is a single page.
>
> This is used by CacheFiles to store the contents of netfs pages into
> their backing file pages.
>
> Supply a generic implementation for this that uses the write_begin()
> and write_end() address_space operations to bind a copy directly into
> the page cache.
>
> Hook the Ext2 and Ext3 operations to the generic implementation.
Actually, it doesn't. I split that out into the next patch, but I forgot to
edit the patch description.
David
WARNING: multiple messages have this Message-ID (diff)
From: David Howells <dhowells@redhat.com>
To: nickpiggin@yahoo.com.au, hch@infradead.org
Cc: dhowells@redhat.com, linux-fsdevel@vger.kernel.org,
nfsv4@linux-nfs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] CacheFiles: Use the ->write() file op rather than a special kernel aop
Date: Fri, 03 Apr 2009 10:51:56 +0100 [thread overview]
Message-ID: <9759.1238752316@redhat.com> (raw)
In-Reply-To: <20090403094138.9510.80681.stgit@warthog.procyon.org.uk>
David Howells <dhowells@redhat.com> wrote:
> This reverts the patch:
>
> CacheFiles: Add a hook to write a single page of data to an inode
>
> Add an address space operation to write one single page of data to an
> inode at a page-aligned location (thus permitting the implementation to
> be highly optimised). The data source is a single page.
>
> This is used by CacheFiles to store the contents of netfs pages into
> their backing file pages.
>
> Supply a generic implementation for this that uses the write_begin()
> and write_end() address_space operations to bind a copy directly into
> the page cache.
>
> Hook the Ext2 and Ext3 operations to the generic implementation.
Actually, it doesn't. I split that out into the next patch, but I forgot to
edit the patch description.
David
next prev parent reply other threads:[~2009-04-03 9:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 9:41 [PATCH 1/4] CacheFiles: Use the ->write() file op rather than a special kernel aop David Howells
2009-04-03 9:41 ` David Howells
2009-04-03 9:41 ` [PATCH 2/4] CacheFiles: Revert the addition of write_one_page() David Howells
2009-04-03 13:50 ` Christoph Hellwig
2009-04-03 13:53 ` David Howells
2009-04-03 13:53 ` David Howells
2009-04-04 5:55 ` Nick Piggin
2009-04-04 5:55 ` Nick Piggin
2009-04-03 9:41 ` [PATCH 3/4] FS-Cache: Use a radix tree to track pages being written rather than a page flag David Howells
2009-04-03 9:41 ` David Howells
2009-04-03 9:41 ` [PATCH 4/4] FS-Cache: Revert the addition of PG_owner_priv2/PG_fscache_write David Howells
2009-04-03 9:41 ` David Howells
2009-04-03 9:51 ` David Howells [this message]
2009-04-03 9:51 ` [PATCH 1/4] CacheFiles: Use the ->write() file op rather than a special kernel aop David Howells
2009-04-03 13:49 ` Christoph Hellwig
2009-04-03 13:57 ` David Howells
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=9759.1238752316@redhat.com \
--to=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfsv4@linux-nfs.org \
--cc=nickpiggin@yahoo.com.au \
/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.