diff options
| author |   Chuck Lever <chuck.lever@oracle.com> | 2020-09-04 17:39:12 -0400 |
|---|---|---|
| committer |   Trond Myklebust <trond.myklebust@hammerspace.com> | 2020-09-05 10:39:41 -0400 |
| commit | 644c9f40cf71969f29add32f32349e71d4995c0b (patch) | |
| tree | b4055becff17fe31230bf1a6be2e20e5759eb6fb /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | NFSv4.1 handle ERR_DELAY error reclaiming locking state on delegation recall (diff) | |
| download | wireguard-linux-644c9f40cf71969f29add32f32349e71d4995c0b.tar.xz wireguard-linux-644c9f40cf71969f29add32f32349e71d4995c0b.zip | |
NFS: Zero-stateid SETATTR should first return delegation
If a write delegation isn't available, the Linux NFS client uses
a zero-stateid when performing a SETATTR.
NFSv4.0 provides no mechanism for an NFS server to match such a
request to a particular client. It recalls all delegations for that
file, even delegations held by the client issuing the request. If
that client happens to hold a read delegation, the server will
recall it immediately, resulting in an NFS4ERR_DELAY/CB_RECALL/
DELEGRETURN sequence.
Optimize out this pipeline bubble by having the client return any
delegations it may hold on a file before it issues a
SETATTR(zero-stateid) on that file.
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions