diff options
author | Mike Snitzer <snitzer@kernel.org> | 2024-11-16 04:41:06 +0300 |
---|---|---|
committer | Anna Schumaker <anna.schumaker@oracle.com> | 2025-01-15 01:05:10 +0300 |
commit | 4a489220aa8c9daf5f02396c28cebade9f9ab563 (patch) | |
tree | c31e883fef1bebba297f7804d3d38c19c731fd8a /tools/perf/scripts/python/gecko.py | |
parent | 76d4cb6345da0f2cd505e552157258325bcc8bcd (diff) | |
download | linux-4a489220aa8c9daf5f02396c28cebade9f9ab563.tar.xz |
nfs: probe for LOCALIO when v3 client reconnects to server
Re-enabling NFSv3 LOCALIO is made more complex (than NFSv4) because v3
is stateless. As such, the hueristic used to identify a LOCALIO probe
point is more adhoc by nature: if/when NFSv3 client IO begins to
complete again in terms of normal RPC-based NFSv3 server IO, attempt
nfs_local_probe_async().
Care is taken to throttle the frequency of nfs_local_probe_async(),
otherwise there could be a flood of repeat calls to
nfs_local_probe_async().
The throttle is admin controlled using a new module parameter for
nfsv3, e.g.:
echo 512 > /sys/module/nfsv3/parameters/nfs3_localio_probe_throttle
Probe for NFSv3 LOCALIO every N IO requests (512 in this case). Must
be power-of-2, defaults to 0 (probing disabled).
On systems that expect to use LOCALIO with NFSv3 the admin should
configure the 'nfs3_localio_probe_throttle' module parameter.
This commit backfills module parameter documentation in localio.rst
Signed-off-by: Mike Snitzer <snitzer@kernel.org>
Reviewed-by: Jeff Layton <jlayton@kernel.org>
Signed-off-by: Anna Schumaker <anna.schumaker@oracle.com>
Diffstat (limited to 'tools/perf/scripts/python/gecko.py')
0 files changed, 0 insertions, 0 deletions