Lines Matching full:server

9 server to reliably handshake to determine if they are on the same
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
32 directly to the server without having to go over the network. The
36 server.
72    a. Workloads where the NFS client and server are on the same host
75       running on the same host as the knfsd server being used for
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
98    server. This sets up a requirement for a handshake protocol that
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
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.
137    works by establishing a context that is cached by the server, and
156    See the detailed "NFS Client and Server Interlock" section below.
163 NFS server can see the nonce (single-use UUID) the client generated and
196 NFS Common and Client/Server Handshake
202 verification by the NFS server and if matched the NFS server populates
210 (e.g. 'net' is the server's network namespace, through it the client can
212 and server synchronization that enables advanced usage and lifetime of
217 NFS Client and Server Interlock
238 This interlock of the NFS client and server has been verified to fix an
246 NFS Client issues IO instead of Server
255 focused use of select nfs server objects to allow a client local to a
256 server to open a file pointer without needing to go over the network.
259 server's fs/nfsd/localio.c:nfsd_open_local_fh() and carefully access
270 done by the nfs server). As such, for these operations, the NFS client
272 the NFS server. See: fs/nfs/localio.c:nfs_local_doio() and
275 With normal NFS that makes use of RPC to issue IO to the server, if an
277 the NFS server will not. The NFS server's use of buffered IO affords
282 the NFS server, by setting the 'localio_O_DIRECT_semantics' nfs module
300 NFS client access to the NFS server is also used for LOCALIO.
303 namespace the server has. This is required to allow the client to access
304 the server's per-namespace nfsd_net struct. With traditional NFS, the
307 altered or purposely extended from the server to the client.
313 controls if LOCALIO is enabled, defaults to Y. If client and server are
333 - Client and server both on the same host.
335 - All permutations of client and server support enablement for both
336   local and remote client and server.
341 - Client on host, server within a container (for both v3 and v4.2).