diff options
| author | Mike Snitzer <snitzer@kernel.org> | 2024-09-05 15:10:00 -0400 |
|---|---|---|
| committer | Anna Schumaker <anna.schumaker@oracle.com> | 2024-09-23 15:03:31 -0400 |
| commit | 736cd2c1ae7f911df9aae0e647899b49bdbccdb8 (patch) | |
| tree | 50673c0e42a599d0c21352f3a1c788282418242f /rust/helpers/task.c | |
| parent | f7128262b15287e4be501e30f9e1f0258606a593 (diff) | |
| download | linux-736cd2c1ae7f911df9aae0e647899b49bdbccdb8.tar.gz linux-736cd2c1ae7f911df9aae0e647899b49bdbccdb8.tar.bz2 linux-736cd2c1ae7f911df9aae0e647899b49bdbccdb8.zip | |
nfs: add "NFS Client and Server Interlock" section to localio.rst
This section answers a new FAQ entry:
9. How does LOCALIO make certain that object lifetimes are managed
properly given NFSD and NFS operate in different contexts?
See the detailed "NFS Client and Server Interlock" section below.
The first half of the section details NeilBrown's elegant design
for LOCALIO's nfs_uuid_t based interlock and is heavily based on
Neil's "net namespace refcounting" description here:
https://marc.info/?l=linux-nfs&m=172498546024767&w=2
The second half of the section details the per-cpu-refcount introduced
to ensure NFSD's nfsd_serv isn't destroyed while in use by a LOCALIO
client.
Signed-off-by: Mike Snitzer <snitzer@kernel.org>
Reviewed-by: NeilBrown <neilb@suse.de>
Reviewed-by: Jeff Layton <jlayton@kernel.org>
Signed-off-by: Anna Schumaker <anna.schumaker@oracle.com>
Diffstat (limited to 'rust/helpers/task.c')
0 files changed, 0 insertions, 0 deletions