From: Jeff Layton <jlayton@primarydata.com>
To: bfields@fieldses.org
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 00/10] sunrpc: fixes and cleanups for svc creation and thread handling
Date: Wed, 19 Nov 2014 07:51:12 -0500 [thread overview]
Message-ID: <1416401482-2562-1-git-send-email-jlayton@primarydata.com> (raw)
Hi Bruce!
Patch #1 in this series is a bugfix, but probably isn't worth sending to
stable. The rest are just cleanups in preparation for some other patches
that I have queued up. Can you consider these for 3.19?
The main one that I'm hoping to send soon for v3.19 is the one to help
reduce the pool->sp_lock contention on busy servers. I have some
preliminary numbers that look pretty good, but one of our QA folks is
working on getting some better ones from a more rigorous test. I'll
send those along in a few days once I have those numbers.
Jeff Layton (10):
sunrpc: release svc_pool_map reference when serv allocation fails
sunrpc: add a generic rq_flags field to svc_rqst and move rq_secure to
it
sunrpc: move rq_local field to rq_flags
sunrpc: move rq_usedeferral flag to rq_flags
sunrpc: move rq_dropme flag into rq_flags
sunrpc: move rq_splice_ok flag into rq_flags
sunrpc: move rq_cachetype field to better optimize space
sunrpc: convert sp_task_pending flag to use atomic bitops
sunrpc: have svc_wake_up only deal with pool 0
sunrpc: require svc_create callers to pass in meaningful shutdown
routine
fs/lockd/svc.c | 2 +-
fs/nfsd/nfs4proc.c | 6 ++---
fs/nfsd/nfs4xdr.c | 8 +++---
fs/nfsd/nfscache.c | 4 +--
fs/nfsd/nfsfh.c | 2 +-
fs/nfsd/nfssvc.c | 2 +-
fs/nfsd/vfs.c | 6 ++---
include/linux/sunrpc/svc.h | 22 +++++++++--------
include/trace/events/sunrpc.h | 24 +++++++++++++-----
net/sunrpc/auth_gss/svcauth_gss.c | 2 +-
net/sunrpc/svc.c | 23 +++++++++---------
net/sunrpc/svc_xprt.c | 51 ++++++++++++++++++---------------------
net/sunrpc/svcsock.c | 5 +++-
13 files changed, 85 insertions(+), 72 deletions(-)
--
2.1.0
next reply other threads:[~2014-11-19 12:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 12:51 Jeff Layton [this message]
2014-11-19 12:51 ` [PATCH 01/10] sunrpc: release svc_pool_map reference when serv allocation fails Jeff Layton
2014-11-19 12:51 ` [PATCH 02/10] sunrpc: add a generic rq_flags field to svc_rqst and move rq_secure to it Jeff Layton
2014-11-19 12:51 ` [PATCH 03/10] sunrpc: move rq_local field to rq_flags Jeff Layton
2014-11-19 12:51 ` [PATCH 04/10] sunrpc: move rq_usedeferral flag " Jeff Layton
2014-11-19 12:51 ` [PATCH 05/10] sunrpc: move rq_dropme flag into rq_flags Jeff Layton
2014-11-19 12:51 ` [PATCH 06/10] sunrpc: move rq_splice_ok " Jeff Layton
2014-11-19 12:51 ` [PATCH 07/10] sunrpc: move rq_cachetype field to better optimize space Jeff Layton
2014-11-19 12:51 ` [PATCH 08/10] sunrpc: convert sp_task_pending flag to use atomic bitops Jeff Layton
2014-11-19 12:51 ` [PATCH 09/10] sunrpc: have svc_wake_up only deal with pool 0 Jeff Layton
2014-11-19 12:51 ` [PATCH 10/10] sunrpc: require svc_create callers to pass in meaningful shutdown routine Jeff Layton
2014-11-19 14:57 ` [PATCH 00/10] sunrpc: fixes and cleanups for svc creation and thread handling J. Bruce Fields
2014-11-19 21:37 ` J. Bruce Fields
2014-11-19 21:59 ` Jeff Layton
2014-11-20 14:17 ` Anna Schumaker
2014-12-01 19:56 ` J. Bruce Fields
2014-12-01 20:08 ` Trond Myklebust
2014-12-01 20:12 ` 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=1416401482-2562-1-git-send-email-jlayton@primarydata.com \
--to=jlayton@primarydata.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