Searched full:server (Results 1 – 25 of 229) sorted by relevance
12345678910
| /Documentation/filesystems/nfs/ |
| D | localio.rst | 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
[all …]
|
| D | client-identifier.rst | 25 Simply put, an NFSv4 server creates a lease for each NFSv4 client.
26 The server collects each client's file open and lock state under
30 While a lease remains valid, the server holding that lease
34 the NFSv4 protocol allows the server to remove the client's open
40 In addition, each NFSv4 server manages a persistent list of client
41 leases. When the server restarts and clients attempt to recover
42 their state, the server uses this list to distinguish amongst
43 clients that held state before the server restarted and clients
45 persist safely across server restarts.
57 server to distinguish successive boot epochs of the same client.
[all …]
|
| D | reexport.rst | 29 case when the reexport server reboots. Clients will lose any locks
36 If the original server uses an X byte filehandle for a given object, the
37 reexport server's filehandle for the reexported object will be X+22
51 NFSv2 if the original server gives you filehandles that fit in 10
55 by an NFS server without asking the server vendor.
58 typical length of the filehandle from a Linux server exporting the given
75 Linux server filehandles are a bit more complicated than this, though;
90 exported from a Linux server. In general, if the original server is
109 server's support has always been incomplete: they are enforced only
111 filesystem locally. A reexport server will also not pass them along to
[all …]
|
| /Documentation/block/ |
| D | ublk.rst | 30 in this document, ``ublk server`` refers to generic ublk userspace
43 assigned by one queue wide unique tag. ublk server assigns unique tag to each
51 done by io_uring, but also the preferred IO handling in ublk server is io_uring
64 ublk requires userspace ublk server to handle real block device logic.
102 Add a ublk char device (``/dev/ublkc*``) which is talked with ublk server
106 for which the info is negotiated with the driver and sent back to the server.
118 After the server prepares userspace resources (such as creating per-queue
126 ublk server will release resources (such as destroying per-queue pthread &
137 that each queue's affinity info is available. The server sends
144 For retrieving device info via ``ublksrv_ctrl_dev_info``. It is the server's
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-rnbd-server | 1 What: /sys/class/rnbd-server
5 Description: provide information about RNBD-server.
7 What: /sys/class/rnbd-server/ctl/
12 block device is created under /sys/class/rnbd-server/ctl/devices/.
14 What: /sys/class/rnbd-server/ctl/devices/<device_name>/block_dev
23 What: /sys/class/rnbd-server/ctl/devices/<device_name>/sessions/
30 /sys/class/rnbd-server/ctl/devices/<device_name>/sessions/<session-name>/
34 What: /sys/class/rnbd-server/ctl/devices/<device_name>/sessions/<session-name>/read_only
40 What: /sys/class/rnbd-server/ctl/devices/<device_name>/sessions/<session-name>/mapping_path
46 What: /sys/class/rnbd-server/ctl/devices/<device_name>/sessions/<session-name>/access_mode
[all …]
|
| D | sysfs-class-rtrs-server | 1 What: /sys/class/rtrs-server
8 What: /sys/class/rtrs-server/<session-name>/paths/
14 on server.
16 What: /sys/class/rtrs-server/<session-name>/paths/<src@dst>/disconnect
23 What: /sys/class/rtrs-server/<session-name>/paths/<src@dst>/hca_name
29 What: /sys/class/rtrs-server/<session-name>/paths/<src@dst>/hca_port
35 What: /sys/class/rtrs-server/<session-name>/paths/<src@dst>/src_addr
41 What: /sys/class/rtrs-server/<session-name>/paths/<src@dst>/dst_addr
47 What: /sys/class/rtrs-server/<session-name>/paths/<src@dst>/stats/rdma
|
| D | sysfs-class-rnbd-client | 33 a given session on the client and on the server.
37 describes a connection between the client and the server by
50 The connection will be established to this server from any client IP address.
63 Path to the block device on the server side. Path is specified
64 relative to the directory on server side configured in the
74 have different devices namespace, e.g. server was configured with
76 client has this string "sessname=blya device_path=sda", then server
81 mapped as "ro" read-only or "rw" read-write. The server allows
105 be found on the server, it will fail with ENOENT.
|
| /Documentation/admin-guide/cifs/ |
| D | usage.rst | 66 and maximum number of simultaneous requests to one server can be configured.
100 //server/usersharename /mnt/username cifs user 0 0
132 to the file /etc/fstab for each //server/share you wish to mount, but
142 (CIFS/SMB1), we recommend using a server that supports the SNIA CIFS
146 not have a server that supports the Unix extensions for CIFS (such as Samba
147 2.2.5 or later). To enable the Unix CIFS Extensions in the Samba server, add
152 to your smb.conf file on the server. Note that the following smb.conf settings
153 are also useful (on the Samba server) when the majority of clients are Unix or
160 Note that server ea support is required for supporting xattrs from the Linux
178 enabled on the server and client, subsequent setattr calls (e.g. chmod) can
[all …]
|
| D | todo.rst | 21 are currently the only two server side copy mechanisms supported)
35 roundtrips to the server and improve performance. Various cases
55 j) Create UID mapping facility so server UIDs can be mapped on a per
56 mount or a per server basis to client UIDs or nobody if no mapping
67 encrypted on the server is reported, but changing the attribute is not
78 move, and server network adapter changes. Currently only notifications by
79 the witness protocol for server move is supported by the Linux client.
113 1) check out max path names and max path name components against various server
|
| D | introduction.rst | 7 protocol which was the successor to the Server Message Block
15 file servers such as Windows (including Windows 2019 Server), as
16 well as by Samba (which provides excellent CIFS/SMB2/SMB3 server
30 improvements. Since both Samba server and this filesystem client support the
|
| /Documentation/netlink/specs/ |
| D | nfsd.yaml | 66 name: server
94 name: server-proto
111 name: server-sock
153 attribute-set: server
165 attribute-set: server
176 attribute-set: server-proto
185 attribute-set: server-proto
193 attribute-set: server-sock
202 attribute-set: server-sock
209 doc: set the current server pool-mode
[all …]
|
| /Documentation/admin-guide/nfs/ |
| D | nfs-rdma.rst | 15 and server software.
17 The NFS/RDMA client was first included in Linux 2.6.24. The NFS/RDMA server
46 The first kernel release to contain both the NFS/RDMA client and server was
102 nfs-utils on the server. Furthermore, only the mount.nfs command from
107 The NFS/RDMA client and server are both included in the mainline Linux
125 - Configure the NFS client and server
128 NFS server support enabled. These and other NFS related configuration
134 are turned on. The NFS/RDMA client and server are configured via the hidden
139 and server will not be built
142 in this case the NFS/RDMA client and server will be built as modules
[all …]
|
| D | pnfs-scsi-server.rst | 3 pNFS SCSI layout server user guide
6 This document describes support for pNFS SCSI layouts in the Linux NFS server.
7 With pNFS SCSI layouts, the NFS server acts as Metadata Server (MDS) for pNFS,
12 To use pNFS SCSI layouts with the Linux NFS server, the exported file
19 On a server built with CONFIG_NFSD_SCSI, the pNFS SCSI volume support is
|
| D | nfsroot.rst | 18 In order to use a diskless system, such as an X-terminal or printer server for
24 of this text 'client' means the diskless system, and 'server' means the NFS
25 server.
49 both the server and the name of the directory on the server to mount as root.
59 nfsroot=[<server-ip>:]<root-dir>[,<nfs-options>]
63 <server-ip> Specifies the IP address of the NFS server.
68 <root-dir> Name of the directory on the server to mount as root.
76 port = as given by server portmap daemon
88 ip=<client-ip>:<server-ip>:<gw-ip>:<netmask>:<hostname>:<device>:<autoconf>:<dns0-ip>:<dns1-ip>:<nt…
109 <server-ip> IP address of the NFS server.
[all …]
|
| D | pnfs-block-server.rst | 2 pNFS block layout server user guide
5 The Linux NFS server now supports the pNFS block layout extension. In this
6 case the NFS server acts as Metadata Server (MDS) for pNFS, which in addition
11 To use pNFS block layouts with the Linux NFS server the exported file
18 On the server, pNFS block volume support is automatically if the file system
23 If the nfsd server needs to fence a non-responding client it calls
|
| D | index.rst | 13 pnfs-block-server
14 pnfs-scsi-server
|
| /Documentation/devicetree/bindings/net/ |
| D | marvell,dfx-server.yaml | 4 $id: http://devicetree.org/schemas/net/marvell,dfx-server.yaml#
7 title: Marvell Prestera DFX server
16 const: marvell,dfx-server
23 - const: marvell,dfx-server
42 # The DFX server may expose clocks described as subnodes
56 compatible = "marvell,dfx-server", "simple-bus";
|
| /Documentation/arch/powerpc/ |
| D | hvcs.rst | 2 HVCS IBM "Hypervisor Virtual Console Server" Installation Guide
36 This is the device driver for the IBM Hypervisor Virtual Console Server,
55 major and minor numbers are associated with each vty-server. Directions
79 <*> IBM Hypervisor Virtual Console Server Support
91 <M> IBM Hypervisor Virtual Console Server Support
114 We think that 1024 is currently a decent maximum number of server adapters
206 is a vty-server device configured for that node.
249 Hotplug add and remove of vty-server adapters affects which /dev/hvcs* node
250 is used to connect to each vty-server adapter. In order to determine which
251 vty-server adapter is associated with which /dev/hvcs* node a special sysfs
[all …]
|
| /Documentation/admin-guide/blockdev/ |
| D | nbd.rst | 9 can use a remote server as one of its block devices. So every time
11 request over TCP to the server, which will reply with the data read.
16 For more information, or to download the nbd-client and nbd-server
20 system, as the nbd-server is completely in userspace. In fact,
21 the nbd-server has been successfully ported to other operating
|
| /Documentation/networking/ |
| D | snmp_counter.rst | 1032 Run the ping command against the public dns server 8.8.8.8::
1059 The Linux server sent an ICMP Echo packet, so IpOutRequests,
1061 server got ICMP Echo Reply from 8.8.8.8, so IpInReceives, IcmpInMsgs,
1076 On server side, we run::
1086 The server listened on tcp 9000 port, the client connected to it, they
1089 On server side, we can find below nstat output::
1104 When the server received the first SYN, it replied a SYN+ACK, and came into
1105 SYN-RCVD state, so TcpPassiveOpens increased 1. The server received
1106 SYN, sent SYN+ACK, received ACK, so server sent 1 packet, received 2
1118 Run nc on server::
[all …]
|
| D | rxrpc.rst | 28 (#) Example server usage.
61 receives a blob (the reply), and the server receives the request and then
68 manage security on the client end. The server end must of necessity be
107 shared between client and server connections (connections have a
139 requested, the server then issues a "challenge" and then the client
142 upon it use that same security. In the event that the server lets a
160 reached the server.
175 make multiple simultaneous calls to the same service. One server socket
194 (#) A server-side connection is shared if the client says it is.
208 (#) A socket is made into a server socket by binding an address with a
[all …]
|
| D | ipvs-sysctl.rst | 29 If set, disable the director function while the server is
39 connection will be delivered to the same real server that was
74 directly when no cache server is available and destination
157 packets when its destination server is not available. It may
159 destination server (because of server overload or wrong
160 detection) and add back the server later, and the connections
161 to the server can continue.
165 destination server is not available, then the client program
175 persistent templates when the destination server is quiescent.
176 This may be useful, when a user makes a destination server
[all …]
|
| /Documentation/filesystems/smb/ |
| D | cifsroot.rst | 23 which is only supported by the Samba server. SMB1 is the older
35 Server configuration
42 server min protocol = NT1
57 cifsroot=//<server-ip>/<share>[,options]
60 located in the <server-ip> and <share> specified in this option.
64 server-ip
65 IPv4 address of the server.
|
| /Documentation/ABI/stable/ |
| D | sysfs-acpi-pmprofile | 22 4 Enterprise Server
23 5 SOHO Server
25 7 Performance Server
|
| /Documentation/filesystems/ |
| D | 9p.rst | 39 For remote file server::
47 For server running on QEMU host with virtio transport::
51 where mount_tag is the tag generated by the server to each of the exported
76 Diod (9pfs server) and the forwarder are on the development host, where
89 Just start the 9pfs capable network server like diod/nfs-ganesha e.g.::
129 uname=name user name to attempt mount as on the remote server. The
130 server may override or ignore this value. Certain user
133 aname=name aname specifies the file tree to access when the server is
146 0b00001000 loose caches (no explicit consistency with server)
165 do not necessarily validate cached values on the server. In other
[all …]
|
12345678910