From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: NeilBrown <neilb@suse.de>
Cc: Andrew Morton <akpm@osdl.org>,
nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 000 of 14] knfsd: Introduction
Date: Thu, 09 Mar 2006 12:10:11 -0500 [thread overview]
Message-ID: <1141924212.8293.52.camel@lade.trondhjem.org> (raw)
In-Reply-To: <20060309174755.24381.patches@notabene>
On Thu, 2006-03-09 at 17:51 +1100, NeilBrown wrote:
> [PATCH 000 of 14] knfsd: Introduction
> [PATCH 001 of 14] knfsd: Change the store of auth_domains to not be a 'cache'.
> [PATCH 002 of 14] knfsd: Break the hard linkage from svc_expkey to svc_export
> [PATCH 003 of 14] knfsd: Get rid of 'inplace' sunrpc caches
> [PATCH 004 of 14] knfsd: Create cache_lookup function instead of using a macro to declare one.
> [PATCH 005 of 14] knfsd: Convert ip_map cache to use the new lookup routine.
> [PATCH 006 of 14] knfsd: Use new cache_lookup for svc_export
> [PATCH 007 of 14] knfsd: Use new cache_lookup for svc_expkey cache.
> [PATCH 008 of 14] knfsd: Use new sunrpc cache for rsi cache
> [PATCH 009 of 14] knfsd: Use new cache code for rsc cache
> [PATCH 010 of 14] knfsd: Use new cache code for name/id lookup caches
> [PATCH 011 of 14] knfsd: An assortment of little fixes to the sunrpc cache code.
> [PATCH 012 of 14] knfsd: Remove DefineCacheLookup
> [PATCH 013 of 14] knfsd: Unexport cache_fresh and fix a small race.
> [PATCH 014 of 14] knfsd: Convert sunrpc_cache to use krefs
Any plans to update Documentation/rpc-cache.txt?
Cheers,
Trond
next prev parent reply other threads:[~2006-03-09 17:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-09 6:51 NeilBrown
2006-03-09 6:51 ` [PATCH 001 of 14] knfsd: Change the store of auth_domains to not be a 'cache' NeilBrown
2006-03-09 16:26 ` Paul Dickson
2006-03-09 6:51 ` [PATCH 002 of 14] knfsd: Break the hard linkage from svc_expkey to svc_export NeilBrown
2006-03-09 6:51 ` [PATCH 003 of 14] knfsd: Get rid of 'inplace' sunrpc caches NeilBrown
2006-03-09 6:51 ` [PATCH 004 of 14] knfsd: Create cache_lookup function instead of using a macro to declare one NeilBrown
2006-03-09 6:51 ` [PATCH 005 of 14] knfsd: Convert ip_map cache to use the new lookup routine NeilBrown
2006-03-09 6:51 ` [PATCH 006 of 14] knfsd: Use new cache_lookup for svc_export NeilBrown
2006-03-09 6:51 ` [PATCH 007 of 14] knfsd: Use new cache_lookup for svc_expkey cache NeilBrown
2006-03-09 6:52 ` [PATCH 008 of 14] knfsd: Use new sunrpc cache for rsi cache NeilBrown
2006-03-09 6:52 ` [PATCH 009 of 14] knfsd: Use new cache code for rsc cache NeilBrown
2006-03-09 6:52 ` [PATCH 010 of 14] knfsd: Use new cache code for name/id lookup caches NeilBrown
2006-03-09 6:52 ` [PATCH 011 of 14] knfsd: An assortment of little fixes to the sunrpc cache code NeilBrown
2006-03-09 6:52 ` [PATCH 012 of 14] knfsd: Remove DefineCacheLookup NeilBrown
2006-03-09 6:52 ` [PATCH 013 of 14] knfsd: Unexport cache_fresh and fix a small race NeilBrown
2006-03-09 6:52 ` [PATCH 014 of 14] knfsd: Convert sunrpc_cache to use krefs NeilBrown
2006-03-09 17:10 ` Trond Myklebust [this message]
2006-03-10 0:54 ` [PATCH 000 of 14] knfsd: Introduction Neil Brown
2006-03-13 11:41 ` [NFS] " Steve Dickson
2006-06-27 7:19 NeilBrown
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=1141924212.8293.52.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
/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
all inboxes | Powered by JetHome®