Lines Matching full:client
8 The LOCALIO auxiliary RPC protocol allows the Linux NFS client and
10 host. Select "NFS client and server support for LOCALIO auxiliary
14 Once an NFS client and server handshake as "local", the client will
29 The robust handshake between local client and server is just the
31 client is able to open files and issue reads, writes and commits
72 a. Workloads where the NFS client and server are on the same host
83 b. Allow client and server to autonomously discover if they are
93 deciding if the NFS client and server are co-located on the same
97 assume that IP addresses will be shared between the client and
100 identify that the client and the server really are running on the
108 advantage of NFS client and server locality. Policy that initiates
109 client IO as closely to the server where the data is stored naturally
115 onus on the server to somehow discover that the client is co-located
118 allows the NFS client to negotiate and leverage locality without
122 6. Why is having the client perform a server-side file OPEN, without
131 client perform a server-side file open, without using RPC, is ideal.
156 See the detailed "NFS Client and Server Interlock" section below.
162 RPC method that allows the Linux NFS client to verify the local Linux
163 NFS server can see the nonce (single-use UUID) the client generated and
168 The UUID_IS_LOCAL method encodes the client generated uuid_t in terms of
196 NFS Common and Client/Server Handshake
199 fs/nfs_common/nfslocalio.c provides interfaces that enable an NFS client
203 members in the nfs_uuid_t struct. The NFS client then uses nfs_common to
209 it has members that point to nfsd memory for direct use by the client
210 (e.g. 'net' is the server's network namespace, through it the client can
211 access nn->nfsd_serv with proper rcu read access). It is this client
214 instances that are connected to nfs client's running on the same local
217 NFS Client and Server Interlock
224 net-ns in the client because that prevents a server container from
236 that can be used to find the client. It does add the 16-byte
238 uuid_t is only used during the initial NFS client and server
251 - The client's nfs_uuid_t is passed to nfsd_open_local_fh() so it
261 nfsd_file handle and then the caller (NFS client) must drop the
272 All told, this elaborate interlock of the NFS client and server has been
274 instance running in a container, with a LOCALIO client mounted, is
275 shutdown. Upon restart of the container and associated NFSD the client
277 to the LOCALIO client's attempting to nfsd_open_local_fh(), using
280 NFS Client issues IO instead of Server
289 focused use of select nfs server objects to allow a client local to a
292 The client's fs/nfs/localio.c:nfs_local_open_fh() will call into the
295 RCU. If nfsd_open_local_fh() finds that the client no longer sees valid
297 to nfs_local_open_fh() and the client will try to reestablish the
300 to reboot while a LOCALIO client is connected to it.
302 Once the client has an open nfsd_file pointer it will issue reads,
304 done by the nfs server). As such, for these operations, the NFS client
310 application uses O_DIRECT the NFS client will bypass the pagecache but
313 issuing IO to the NFS client. LOCALIO can be configured to use O_DIRECT
331 NFS client access to the NFS server is also used for LOCALIO.
333 Relative to containers, LOCALIO gives the client access to the network
334 namespace the server has. This is required to allow the client to access
336 client is afforded this same level of access (albeit in terms of the NFS
338 altered or purposely extended from the server to the client.
346 - Client and server both on the same host.
348 - All permutations of client and server support enablement for both
349 local and remote client and server.
354 - Client on host, server within a container (for both v3 and v4.2).