From: Dai Ngo <dai.ngo@oracle.com>
To: chuck.lever@oracle.com, jlayton@kernel.org
Cc: linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [PATCH v3 0/2] NFSD: recall write delegation on GETATTR conflict
Date: Tue, 30 May 2023 19:35:05 -0700 [thread overview]
Message-ID: <1685500507-23598-1-git-send-email-dai.ngo@oracle.com> (raw)
This patch series adds the recall of write delegation when there is
conflict with a GETATTR and a counter in /proc/net/rpc/nfsd to keep
count of this recall.
Changes from v1:
- add comment for nfsd4_deleg_getattr_conflict
- only wait 30ms for delegation to be returned before returing
NFS4ERR_DELAY
- fix test robot undeclared NFSD_STATS_WDELEG_GETATTR error
Changes from v2:
- call nfsd_open_break_lease for non-nfs lease with F_WRLCK
next reply other threads:[~2023-05-31 2:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 2:35 Dai Ngo [this message]
2023-05-31 2:35 ` [PATCH v3 1/2] NFSD: handle GETATTR conflict with write delegation Dai Ngo
2023-05-31 10:11 ` Jeff Layton
2023-05-31 2:35 ` [PATCH v3 2/2] NFSD: add counter for write delegation recall due to conflict with GETATTR Dai Ngo
2023-05-31 10:12 ` Jeff Layton
2023-05-31 14:11 ` Chuck Lever III
2023-05-31 17:46 ` [PATCH v3 0/2] NFSD: recall write delegation on GETATTR conflict Chuck Lever III
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=1685500507-23598-1-git-send-email-dai.ngo@oracle.com \
--to=dai.ngo@oracle.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@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 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).