diff options
author | Steve French <stfrench@microsoft.com> | 2022-08-11 07:53:00 +0200 |
---|---|---|
committer | Steve French <stfrench@microsoft.com> | 2022-08-12 03:03:04 +0200 |
commit | 5efdd9122eff772eae2feae9f0fc0ec02d4846a3 (patch) | |
tree | 14aa11d0dc51b6f62f8487bbc30729f386b3f7ea /crypto/md4.c | |
parent | cifs: Do not use tcon->cfid directly, use the cfid we get from open_cached_dir (diff) | |
download | linux-5efdd9122eff772eae2feae9f0fc0ec02d4846a3.tar.xz linux-5efdd9122eff772eae2feae9f0fc0ec02d4846a3.zip |
smb3: allow deferred close timeout to be configurable
Deferred close can be a very useful feature for allowing
caching data for read, and for minimizing the number of
reopens needed for a file that is repeatedly opened and
close but there are workloads where its default (1 second,
similar to actimeo/acregmax) is much too small.
Allow the user to configure the amount of time we can
defer sending the final smb3 close when we have a
handle lease on the file (rather than forcing it to depend
on value of actimeo which is often unrelated, and less safe).
Adds new mount parameter "closetimeo=" which is the maximum
number of seconds we can wait before sending an SMB3
close when we have a handle lease for it. Default value
also is set to slightly larger at 5 seconds (although some
other clients use larger default this should still help).
Suggested-by: Bharath SM <bharathsm@microsoft.com>
Reviewed-by: Bharath SM <bharathsm@microsoft.com>
Reviewed-by: Shyam Prasad N <sprasad@microsoft.com>
Reviewed-by: Paulo Alcantara (SUSE) <pc@cjr.nz>
Signed-off-by: Steve French <stfrench@microsoft.com>
Diffstat (limited to 'crypto/md4.c')
0 files changed, 0 insertions, 0 deletions