Linux NFS development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@redhat.com>
To: bfields@fieldses.org
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH v10 2/8] nfsd: add nfsd4_client_tracking_ops struct and a way to set it
Date: Wed, 21 Mar 2012 19:59:46 -0400	[thread overview]
Message-ID: <20120321195946.67c88cf9@redhat.com> (raw)
In-Reply-To: <1332337929-18580-3-git-send-email-jlayton@redhat.com>

On Wed, 21 Mar 2012 09:52:03 -0400
Jeff Layton <jlayton@redhat.com> wrote:

> Abstract out the mechanism that we use to track clients into a set of
> client name tracking functions.
> 
> This gives us a mechanism to plug in a new set of client tracking
> functions without disturbing the callers. It also gives us a way to
> decide on what tracking scheme to use at runtime.
> 
> For now, this just looks like pointless abstraction, but later we'll
> add a new alternate scheme for tracking clients on stable storage.
> 
> Note too that this patch anticipates the eventual containerization
> of this code by passing in struct net pointers in places. No attempt
> is made to containerize the legacy client tracker however.
> 
> Signed-off-by: Jeff Layton <jlayton@redhat.com>
> ---
>  fs/nfsd/nfs4recover.c |  136 +++++++++++++++++++++++++++++++++++++++++++++----
>  fs/nfsd/nfs4state.c   |   61 +++++++---------------
>  fs/nfsd/state.h       |   15 +++--
>  3 files changed, 155 insertions(+), 57 deletions(-)
> 

Bruce pointed out that I missed converting a spot in the new fault
injection code, so I've followed this up with a v11 patch that fixes
that problem.

Cheers!
-- 
Jeff Layton <jlayton@redhat.com>

  parent reply	other threads:[~2012-03-21 23:59 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-21 13:52 [PATCH v10 0/8] nfsd: overhaul the client name tracking code Jeff Layton
2012-03-21 13:52 ` [PATCH v10 1/8] nfsd: convert nfs4_client->cl_cb_flags to a generic flags field Jeff Layton
2012-03-21 20:41   ` J. Bruce Fields
2012-03-21 20:52     ` Jeff Layton
2012-03-21 21:05       ` J. Bruce Fields
2012-03-21 13:52 ` [PATCH v10 2/8] nfsd: add nfsd4_client_tracking_ops struct and a way to set it Jeff Layton
2012-03-21 20:42   ` [PATCH v11 " Jeff Layton
2012-03-21 23:59   ` Jeff Layton [this message]
2012-03-21 13:52 ` [PATCH v10 3/8] sunrpc: create nfsd dir in rpc_pipefs Jeff Layton
2012-03-23 12:12   ` J. Bruce Fields
2012-03-23 13:31     ` J. Bruce Fields
2012-03-23 15:20       ` Myklebust, Trond
2012-03-23 15:22         ` J. Bruce Fields
2012-03-23 15:34           ` Myklebust, Trond
2012-03-23 15:53             ` Jeff Layton
2012-03-23 16:12               ` Jeff Layton
2012-03-23 17:04                 ` J. Bruce Fields
2012-03-28 23:09                   ` [PATCH] nfsd4: use auth_unix unconditionally on backchannel J. Bruce Fields
2012-03-28 23:16                     ` Myklebust, Trond
2012-03-28 23:46                       ` J. Bruce Fields
2012-03-29 14:29                         ` Matt W. Benjamin
2012-03-29 14:29                           ` Matt W. Benjamin
2012-03-29 14:48                           ` J. Bruce Fields
2012-03-23 16:00             ` [PATCH v10 3/8] sunrpc: create nfsd dir in rpc_pipefs J. Bruce Fields
2012-03-21 13:52 ` [PATCH v10 4/8] nfsd: add a per-net-namespace struct for nfsd Jeff Layton
2012-03-21 13:52 ` [PATCH v10 5/8] nfsd: add a header describing upcall to nfsdcld Jeff Layton
2012-03-21 13:52 ` [PATCH v10 6/8] nfsd: add the infrastructure to handle the cld upcall Jeff Layton
2012-03-21 13:52 ` [PATCH v10 7/8] nfsd: add notifier to handle mount/unmount of rpc_pipefs sb Jeff Layton
2012-03-21 13:52 ` [PATCH v10 8/8] nfsd: don't allow legacy client tracker init for anything but init_net Jeff Layton
2012-03-23 17:06 ` [PATCH v10 0/8] nfsd: overhaul the client name tracking code J. Bruce Fields
2012-03-23 17:26   ` Jeff Layton
2012-03-26 20:02     ` J. Bruce Fields
2012-03-27 15:06       ` J. Bruce Fields

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=20120321195946.67c88cf9@redhat.com \
    --to=jlayton@redhat.com \
    --cc=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    /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