From: Stanislav Kinsbursky <skinsbursky@parallels.com>
To: bfields@fieldses.org
Cc: linux-nfs@vger.kernel.org, Trond.Myklebust@netapp.com,
linux-kernel@vger.kernel.org, devel@openvz.org
Subject: [PATCH 0/5] nfsd: more NFSv4 state containerization
Date: Mon, 26 Nov 2012 15:21:49 +0300 [thread overview]
Message-ID: <20121126121907.955.25349.stgit@localhost.localdomain> (raw)
This patch set makes NFSv4 state created and destroyed per net and thus
completes it's containerization (the only exceprtion is client_mutex, but this
one a hard nut to crack).
Note: patch set depend on previously sent patch named "nfsd4: remove state
lock from nfs4_state_shutdown".
The following series implements...
---
Stanislav Kinsbursky (5):
nfsd: make client_lock per net
nfsd: make delegations shutdown network namespace aware
nfsd: cleanup NFSd state shutdown a bit
nfsd: cleanup NFSd state start a bit
nfsd: call state init and shutdown twice
fs/nfsd/netns.h | 3 +
fs/nfsd/nfs4state.c | 137 +++++++++++++++++++++++++++++----------------------
fs/nfsd/nfsd.h | 4 +
fs/nfsd/nfssvc.c | 15 +++++-
4 files changed, 99 insertions(+), 60 deletions(-)
next reply other threads:[~2012-11-26 12:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 12:21 Stanislav Kinsbursky [this message]
2012-11-26 12:21 ` [PATCH 1/5] nfsd: make client_lock per net Stanislav Kinsbursky
2012-11-26 12:22 ` [PATCH 2/5] nfsd: make delegations shutdown network namespace aware Stanislav Kinsbursky
2012-11-26 12:22 ` [PATCH 3/5] nfsd: cleanup NFSd state shutdown a bit Stanislav Kinsbursky
2012-11-26 12:22 ` [PATCH 4/5] nfsd: cleanup NFSd state start " Stanislav Kinsbursky
2012-11-26 12:22 ` [PATCH 5/5] nfsd: call state init and shutdown twice Stanislav Kinsbursky
2012-11-27 22:29 ` [PATCH 0/5] nfsd: more NFSv4 state containerization 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=20121126121907.955.25349.stgit@localhost.localdomain \
--to=skinsbursky@parallels.com \
--cc=Trond.Myklebust@netapp.com \
--cc=bfields@fieldses.org \
--cc=devel@openvz.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.