From: Jeff Garzik <jeff@garzik.org>
To: Chuck Lever <chucklever@gmail.com>
Cc: David Howells <dhowells@redhat.com>,
torvalds@osdl.org, akpm@osdl.org, steved@redhat.com,
trond.myklebust@fys.uio.no, linux-fsdevel@vger.kernel.org,
linux-cachefs@redhat.com, nfsv4@linux-nfs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/7] NFS: Use local caching [try #12]
Date: Fri, 18 Aug 2006 14:41:58 -0400 [thread overview]
Message-ID: <44E609F6.1090603@garzik.org> (raw)
In-Reply-To: <76bd70e30608180843m536e9f57y90e1915f40f85b2@mail.gmail.com>
Chuck Lever wrote:
> Hi David-
>
> On 8/18/06, David Howells <dhowells@redhat.com> wrote:
>> The attached patch makes it possible for the NFS filesystem to make
>> use of the
>> network filesystem local caching service (FS-Cache).
>>
>> To be able to use this, an updated mount program is required. This
>> can be
>> obtained from:
>>
>> http://people.redhat.com/steved/cachefs/util-linux/
>>
>> To mount an NFS filesystem to use caching, add an "fsc" option to the
>> mount:
>>
>> mount warthog:/ /a -o fsc
>>
>> Signed-Off-By: David Howells <dhowells@redhat.com>
>> ---
>>
>> fs/Kconfig | 7 +
>> fs/nfs/Makefile | 1
>> fs/nfs/client.c | 11 +
>> fs/nfs/file.c | 49 ++++-
>> fs/nfs/fscache.c | 348 ++++++++++++++++++++++++++++++++
>> fs/nfs/fscache.h | 476
>> ++++++++++++++++++++++++++++++++++++++++++++
>> fs/nfs/inode.c | 21 ++
>> fs/nfs/internal.h | 32 +++
>> fs/nfs/pagelist.c | 3
>> fs/nfs/read.c | 30 +++
>> fs/nfs/super.c | 1
>> fs/nfs/sysctl.c | 43 ++++
>> fs/nfs/write.c | 11 +
>> include/linux/nfs4_mount.h | 1
>> include/linux/nfs_fs.h | 5
>> include/linux/nfs_fs_sb.h | 5
>> include/linux/nfs_mount.h | 1
>> 17 files changed, 1035 insertions(+), 10 deletions(-)
>>
>> diff --git a/fs/nfs/fscache.c b/fs/nfs/fscache.c
>> new file mode 100644
>> index 0000000..94d5e3a
>> --- /dev/null
>> +++ b/fs/nfs/fscache.c
>> @@ -0,0 +1,348 @@
>> +/* fscache.c: NFS filesystem cache interface
>> + *
>> + * Copyright (C) 2006 Red Hat, Inc. All Rights Reserved.
>> + * Written by David Howells (dhowells@redhat.com)
>> + *
>
>> +
>> +static uint16_t nfs_server_get_key(const void *cookie_netfs_data,
>> + void *buffer, uint16_t bufmax)
>> +{
>
> Why don't you use the function declaration style that is used in the
> rest of the NFS client? All the parameters belong on one line, don't
> they?
Normally, one wraps the line if it exceeds 80 columns...
Jeff
next prev parent reply other threads:[~2006-08-18 18:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 15:35 [PATCH 0/7] Permit filesystem local caching and NFS superblock sharing [try #12] David Howells
2006-08-18 15:35 ` [PATCH 1/7] FS-Cache: Provide a filesystem-specific sync'able page bit " David Howells
2006-08-18 15:35 ` [PATCH 3/7] FS-Cache: Release page->private after failed readahead " David Howells
2006-08-18 15:35 ` [PATCH 4/7] FS-Cache: Make kAFS use FS-Cache " David Howells
2006-08-18 15:35 ` [PATCH 5/7] NFS: Use local caching " David Howells
2006-08-18 15:43 ` Chuck Lever
2006-08-18 15:51 ` David Howells
2006-08-18 18:41 ` Jeff Garzik [this message]
2006-08-18 15:35 ` [PATCH 6/7] FS-Cache: CacheFiles: ia64: missing copy_page export " 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=44E609F6.1090603@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@osdl.org \
--cc=chucklever@gmail.com \
--cc=dhowells@redhat.com \
--cc=linux-cachefs@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfsv4@linux-nfs.org \
--cc=steved@redhat.com \
--cc=torvalds@osdl.org \
--cc=trond.myklebust@fys.uio.no \
/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