linux-kernel.vger.kernel.org archive mirror
 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: make service created per net
Date: Mon, 10 Dec 2012 15:18:15 -0500	[thread overview]
Message-ID: <20121210201815.GA17350@fieldses.org> (raw)
In-Reply-To: <20121206111903.29559.4853.stgit@localhost.localdomain>

On Thu, Dec 06, 2012 at 02:22:57PM +0300, Stanislav Kinsbursky wrote:
> This patch set prepares service control to be able to start separated
> independent NFSd services in different network namespace environments.
> Key changes are:
> 1) Create independent instances of NFSd service (and thus threads pool) for
> each network namespace.
> 2) Control generic resources allocation and destruction by usage counter.
> 3) Cleanup and simplify Nfsd service start and shutdown.
> 4) Move some more NFSd state parts (like boot_time and "nfsd is up" flag to
> per-net data).

OK, thanks, applying.--b.

> 
> The following series implements...
> 
> ---
> 
> Stanislav Kinsbursky (8):
>       nfsd: move per-net startup code to separated function
>       nfsd: per-net NFSd up flag introduced
>       nfsd: make NFSd service boot time per-net
>       nfsd: make NFSd service structure allocated per net
>       nfsd: introduce helpers for generic resources init and shutdown
>       nfsd: simplify NFSv4 state init and shutdown
>       nfsd: replace boolean nfsd_up flag by users counter
>       nfsd: simplify service shutdown
> 
> 
>  fs/nfsd/netns.h     |    9 ++
>  fs/nfsd/nfs3xdr.c   |   14 +++-
>  fs/nfsd/nfs4proc.c  |   11 ++-
>  fs/nfsd/nfs4state.c |   14 ++--
>  fs/nfsd/nfsctl.c    |   63 ++++++++++-------
>  fs/nfsd/nfsd.h      |   23 +-----
>  fs/nfsd/nfssvc.c    |  185 +++++++++++++++++++++++++++++++++------------------
>  7 files changed, 195 insertions(+), 124 deletions(-)
> 

      parent reply	other threads:[~2012-12-10 20:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-06 11:22 [PATCH 0/8] nfsd: make service created per net Stanislav Kinsbursky
2012-12-06 11:23 ` [PATCH 1/8] nfsd: move per-net startup code to separated function Stanislav Kinsbursky
2012-12-06 11:23 ` [PATCH 2/8] nfsd: per-net NFSd up flag introduced Stanislav Kinsbursky
2012-12-06 11:23 ` [PATCH 3/8] nfsd: make NFSd service boot time per-net Stanislav Kinsbursky
2012-12-06 11:23 ` [PATCH 4/8] nfsd: make NFSd service structure allocated per net Stanislav Kinsbursky
2012-12-06 11:23 ` [PATCH 5/8] nfsd: introduce helpers for generic resources init and shutdown Stanislav Kinsbursky
2012-12-06 11:23 ` [PATCH 6/8] nfsd: simplify NFSv4 state " Stanislav Kinsbursky
2012-12-06 11:23 ` [PATCH 7/8] nfsd: replace boolean nfsd_up flag by users counter Stanislav Kinsbursky
2012-12-06 11:23 ` [PATCH 8/8] nfsd: simplify service shutdown Stanislav Kinsbursky
2012-12-10 20:18 ` J. Bruce Fields [this message]

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=20121210201815.GA17350@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;
as well as URLs for NNTP newsgroup(s).