From: Jeff Layton <jlayton@redhat.com>
To: bfields@fieldses.org
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH v2 0/4] nfsd: add CB_NOTIFY_LOCK support to knfsd
Date: Tue, 6 Sep 2016 11:04:46 -0400 [thread overview]
Message-ID: <1473174290-29612-1-git-send-email-jlayton@redhat.com> (raw)
This is a small revision to the patch series I sent around a month ago
to add CB_NOTIFY_LOCK support to knfsd. The only real difference here
is a couple of small bugfixes.
The basic idea is to just add support for CB_NOTIFY_LOCK callbacks,
which just tell the client that it may want to retry a lock again
once it becomes available.
Tested in conjunction with the client-side patch series that I will
be sending shortly.
Jeff Layton (4):
nfsd: plumb in a CB_NOTIFY_LOCK operation
nfsd: have nfsd4_lock use blocking locks for v4.1+ locks
nfsd: add a LRU list for blocked locks
nfsd: set the MAY_NOTIFY_LOCK flag in OPEN replies
fs/nfsd/netns.h | 1 +
fs/nfsd/nfs4callback.c | 57 ++++++++++++
fs/nfsd/nfs4state.c | 232 ++++++++++++++++++++++++++++++++++++++++++----
fs/nfsd/state.h | 21 ++++-
fs/nfsd/xdr4cb.h | 9 ++
include/uapi/linux/nfs4.h | 5 +-
6 files changed, 301 insertions(+), 24 deletions(-)
--
2.7.4
next reply other threads:[~2016-09-06 15:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 15:04 Jeff Layton [this message]
2016-09-06 15:04 ` [PATCH v2 1/4] nfsd: plumb in a CB_NOTIFY_LOCK operation Jeff Layton
2016-09-06 15:04 ` [PATCH v2 2/4] nfsd: have nfsd4_lock use blocking locks for v4.1+ locks Jeff Layton
2016-09-06 15:04 ` [PATCH v2 3/4] nfsd: add a LRU list for blocked locks Jeff Layton
2016-09-06 15:04 ` [PATCH v2 4/4] nfsd: set the MAY_NOTIFY_LOCK flag in OPEN replies Jeff Layton
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=1473174290-29612-1-git-send-email-jlayton@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;
as well as URLs for NNTP newsgroup(s).