public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Stanislav Kinsbursky <skinsbursky@parallels.com>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	devel@openvz.org
Subject: Re: [PATCH 0/8] NFSd: precursor and cleanup patch set
Date: Thu, 29 Mar 2012 10:32:18 -0400	[thread overview]
Message-ID: <20120329143218.GI16938@fieldses.org> (raw)
In-Reply-To: <20120328150152.2646.33607.stgit@localhost6.localdomain6>

On Wed, Mar 28, 2012 at 07:08:53PM +0400, Stanislav Kinsbursky wrote:
> This patch set prepares ground for making NFSd export and expkey caches
> allocated and registered per network namespace context.
> Mainly, it just replaces hard-coded pointers with dereferenced everywhere
> required.

Thanks.  I'll be travelling next week and may not get to look at this
till I get back.

--b.

> 
> The following series consists of:
> 
> ---
> 
> Stanislav Kinsbursky (8):
>       nfsd: use passed cache_detail pointer expkey_parse()
>       nfsd: add link to owner cache detail to svc_export structure
>       nfsd: use cache detail pointer from svc_export structure on cache put
>       nfsd: use exp_put() for svc_export_cache put
>       nfsd: pass svc_export_cache pointer as private data to "exports" seq file ops
>       nfsd: use hash table from cache detail in nfsd export seq ops
>       nfsd: pass pointer to export cache down to stack wherever possible.
>       nfsd: pass pointer to expkey cache down to stack wherever possible.
> 
> 
>  fs/nfsd/export.c            |  102 ++++++++++++++++++++++++-------------------
>  fs/nfsd/nfsctl.c            |   11 ++++-
>  fs/nfsd/nfsfh.c             |    2 -
>  include/linux/nfsd/export.h |    3 +
>  4 files changed, 71 insertions(+), 47 deletions(-)
> 

  parent reply	other threads:[~2012-03-29 14:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-28 15:08 [PATCH 0/8] NFSd: precursor and cleanup patch set Stanislav Kinsbursky
2012-03-28 15:09 ` [PATCH 1/8] nfsd: use passed cache_detail pointer expkey_parse() Stanislav Kinsbursky
2012-03-28 15:09 ` [PATCH 2/8] nfsd: add link to owner cache detail to svc_export structure Stanislav Kinsbursky
2012-03-28 15:09 ` [PATCH 3/8] nfsd: use cache detail pointer from svc_export structure on cache put Stanislav Kinsbursky
2012-03-28 15:09 ` [PATCH 4/8] nfsd: use exp_put() for svc_export_cache put Stanislav Kinsbursky
2012-04-11 14:16   ` J. Bruce Fields
2012-04-11 14:41     ` Stanislav Kinsbursky
2012-03-28 15:09 ` [PATCH 5/8] nfsd: pass svc_export_cache pointer as private data to "exports" seq file ops Stanislav Kinsbursky
2012-03-28 15:09 ` [PATCH 6/8] nfsd: use hash table from cache detail in nfsd export seq ops Stanislav Kinsbursky
2012-03-28 15:09 ` [PATCH 7/8] nfsd: pass pointer to export cache down to stack wherever possible Stanislav Kinsbursky
2012-03-28 15:09 ` [PATCH 8/8] nfsd: pass pointer to expkey " Stanislav Kinsbursky
2012-03-29 14:32 ` J. Bruce Fields [this message]
2012-03-29 15:36   ` [PATCH 0/8] NFSd: precursor and cleanup patch set Stanislav Kinsbursky
2012-04-11 16:05 ` J. Bruce Fields
2012-04-11 16:06   ` Stanislav Kinsbursky

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=20120329143218.GI16938@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=devel@openvz.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=skinsbursky@parallels.com \
    /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