From: Trond Myklebust <trond.myklebust@primarydata.com>
To: linux-nfs@vger.kernel.org
Subject: [PATCH 0/6] NFSv4 backchannel improvements
Date: Mon, 29 Aug 2016 20:03:46 -0400 [thread overview]
Message-ID: <1472515432-54202-1-git-send-email-trond.myklebust@primarydata.com> (raw)
Add functionality to allow multiple client backchannel threads and
allow tuning of the advertised backchannel slot table size.
Note: the very first patch is actually a fix for an existing Oopsable
condition, and so should probably be pushed into Linux 4.8...
Trond Myklebust (6):
NFSv4.x: Fix a refcount leak in nfs_callback_up_net
NFSv4.x: Set up struct svc_serv_ops for the callback channel
SUNRPC: Initialise struct svc_serv backchannel fields during
__svc_create()
NFSv4.x: Fix up the global tracking of the callback server
NFSv4.x: Switch to using svc_set_num_threads() to manage the callback
threads
NFSv4.x: Add kernel parameter to control the callback server
Documentation/kernel-parameters.txt | 12 ++++
fs/nfs/callback.c | 137 +++++++++++++++---------------------
fs/nfs/callback.h | 3 +
fs/nfs/nfs4_fs.h | 1 +
fs/nfs/nfs4proc.c | 7 +-
fs/nfs/nfs4session.h | 1 +
fs/nfs/super.c | 10 +++
net/sunrpc/svc.c | 17 +++++
8 files changed, 102 insertions(+), 86 deletions(-)
--
2.7.4
next reply other threads:[~2016-08-30 0:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-30 0:03 Trond Myklebust [this message]
2016-08-30 0:03 ` [PATCH 1/6] NFSv4.x: Fix a refcount leak in nfs_callback_up_net Trond Myklebust
2016-08-30 0:03 ` [PATCH 2/6] NFSv4.x: Set up struct svc_serv_ops for the callback channel Trond Myklebust
2016-08-30 0:03 ` [PATCH 3/6] SUNRPC: Initialise struct svc_serv backchannel fields during __svc_create() Trond Myklebust
2016-08-30 0:03 ` [PATCH 4/6] NFSv4.x: Fix up the global tracking of the callback server Trond Myklebust
2016-08-30 0:03 ` [PATCH 5/6] NFSv4.x: Switch to using svc_set_num_threads() to manage the callback threads Trond Myklebust
2016-08-30 0:03 ` [PATCH 6/6] NFSv4.x: Add kernel parameter to control the callback server Trond Myklebust
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=1472515432-54202-1-git-send-email-trond.myklebust@primarydata.com \
--to=trond.myklebust@primarydata.com \
--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;
as well as URLs for NNTP newsgroup(s).