Searched +full:server +full:- +full:side (Results 1 – 25 of 63) sorted by relevance
123
| /Documentation/networking/ |
| D | snmp_counter.rst | 17 .. _RFC1213 ipInReceives: https://tools.ietf.org/html/rfc1213#page-26 30 .. _RFC1213 ipInDelivers: https://tools.ietf.org/html/rfc1213#page-28 41 .. _RFC1213 ipOutRequests: https://tools.ietf.org/html/rfc1213#page-28 60 .. _Explicit Congestion Notification: https://tools.ietf.org/html/rfc3168#page-6 73 .. _RFC1213 ipInHdrErrors: https://tools.ietf.org/html/rfc1213#page-27 81 .. _RFC1213 ipInAddrErrors: https://tools.ietf.org/html/rfc1213#page-27 98 .. _RFC1213 ipInUnknownProtos: https://tools.ietf.org/html/rfc1213#page-27 111 .. _RFC1213 ipInDiscards: https://tools.ietf.org/html/rfc1213#page-28 118 .. _RFC1213 ipOutDiscards: https://tools.ietf.org/html/rfc1213#page-28 125 .. _RFC1213 ipOutNoRoutes: https://tools.ietf.org/html/rfc1213#page-29 [all …]
|
| D | rxrpc.rst | 1 .. SPDX-License-Identifier: GPL-2.0 7 The RxRPC protocol driver provides a reliable two-phase transport on top of UDP 28 (#) Example server usage. 38 RxRPC is a two-layer protocol. There is a session layer which provides 44 +-------------+ 46 +-------------+ 48 +-------------+ 50 +-------------+ 52 +-------------+ 60 (2) A two-phase protocol. The client transmits a blob (the request) and then [all …]
|
| D | tls-handshake.rst | 1 .. SPDX-License-Identifier: GPL-2.0 4 In-Kernel TLS Handshake 11 over TCP. TLS provides end-to-end data integrity and confidentiality in 21 implementations so that in-kernel TLS consumers do not need to be 46 A kernel TLS consumer initiates a client-side TLS handshake on an open 50 .. code-block:: c 68 instantiated a struct file in sock->file. 75 The consumer can provide a NUL-terminated hostname in the @ta_peername 77 the DNS hostname associated with the server's IP address is used instead. 85 keys, and pre-shared keys are provided to the handshake agent in keys [all …]
|
| D | dccp.rst | 1 .. SPDX-License-Identifier: GPL-2.0 9 - Introduction 10 - Missing features 11 - Socket options 12 - Sysctl variables 13 - IOCTLs 14 - Other tunables 15 - Notes 22 for real-time and multimedia (streaming) traffic. 26 implementation, this is the TCP-like CCID2 (RFC 4341). Additional CCIDs, such as [all …]
|
| D | devmem.rst | 1 .. SPDX-License-Identifier: GPL-2.0 16 ----------- 22 - Distributed training, where ML accelerators, such as GPUs on different hosts, 25 - Distributed raw block storage applications transfer large amounts of data with 28 Typically the Device-to-Device data transfers in the network are implemented as 29 the following low-level operations: Device-to-Host copy, Host-to-Host network 30 transfer, and Host-to-Device copy. 46 - Alleviate host memory bandwidth pressure, compared to existing 47 network-transfer + device-copy semantics. 49 - Alleviate PCIe bandwidth pressure, by limiting data transfer to the lowest [all …]
|
| D | mptcp.rst | 1 .. SPDX-License-Identifier: GPL-2.0 11 `RFC 8684 (MPTCPv1) <https://www.rfc-editor.org/rfc/rfc8684.html>`_. It allows a 15 fail-over if one path is down, and the traffic is seamlessly reinjected on other 26 brings new use-cases, compared to TCP: 28 - Seamless handovers: switching from one path to another while preserving 29 established connections, e.g. to be used in mobility use-cases, like on 31 - Best network selection: using the "best" available path depending on some 33 - Network aggregation: using multiple paths at the same time to have a higher 41 (Linux-specific), a *subflow* (or *path*) is created. This *subflow* consists of 56 ------------ [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 21 block_dev -> ../../../../class/block/ram0 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 38 Description: Contains '1' if device is mapped read-only, otherwise '0'. [all …]
|
| D | sysfs-class-rtrs-server | 1 What: /sys/class/rtrs-server 5 Description: When a user of RTRS API creates a new session on a client side, a 8 What: /sys/class/rtrs-server/<session-name>/paths/ 12 Description: When new path is created by writing to "add_path" entry on client side, 14 on server. 16 What: /sys/class/rtrs-server/<session-name>/paths/<src@dst>/disconnect 21 Operations is non-blocking and returns control immediately to the caller. 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 [all …]
|
| D | sysfs-class-rnbd-client | 1 What: /sys/class/rnbd-client 5 Description: Provide information about RNBD-client. 6 All sysfs files that are not read-only provide the usage information on read: 10 # cat /sys/class/rnbd-client/ctl/map_device 13 > [path=<[srcaddr,]dstaddr>] device_path=<full path on remote side> 18 What: /sys/class/rnbd-client/ctl/map_device 26 device_path=<full path on remote side> 33 a given session on the client and on the server. 34 I.e. "clt_hostname-srv_hostname" could be a natural choice. 37 describes a connection between the client and the server by [all …]
|
| /Documentation/networking/device_drivers/ethernet/microsoft/ |
| D | netvsc.rst | 1 .. SPDX-License-Identifier: GPL-2.0 4 Hyper-V network driver 10 This driver is compatible with Windows Server 2012 R2, 2016 and 17 ---------------- 19 Hyper-V host version does. Windows Server 2016 and Azure 21 IPv6. Windows Server 2012 only supports checksum offload for TCP. 23 Receive Side Scaling 24 -------------------- 25 Hyper-V supports receive side scaling. For TCP & UDP, packets can 41 ethtool -N eth0 rx-flow-hash udp4 sdfn [all …]
|
| /Documentation/security/tpm/ |
| D | tpm_vtpm_proxy.rst | 24 character device ``/dev/tpmX`` (with X=0,1,2...) and a 'server side' file 35 The result of the ioctl are the file descriptor for the 'server side' 47 .. kernel-doc:: include/uapi/linux/vtpm_proxy.h 49 .. kernel-doc:: drivers/char/tpm/tpm_vtpm_proxy.c
|
| /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 26 But unlike the LOCALIO protocol, the sockaddr-based matching didn't 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. 42 - With LOCALIO: 48 - Without LOCALIO: 55 - With LOCALIO: [all …]
|
| /Documentation/filesystems/ |
| D | 9p.rst | 1 .. SPDX-License-Identifier: GPL-2.0 26 http://xcpu.org/papers/xcpu-talk.pdf 30 http://xcpu.org/papers/cellfs-talk.pdf 33 * VirtFS: A Virtualization Aware File System pass-through 34 https://kernel.org/doc/ols/2010/ols2010-pages-109-120.pdf 39 For remote file server:: 41 mount -t 9p 10.10.1.2 /mnt/9 45 mount -t 9p `namespace`/acme /mnt/9 -o trans=unix,uname=$USER 47 For server running on QEMU host with virtio transport:: 49 mount -t 9p -o trans=virtio <mount_tag> /mnt/9 [all …]
|
| D | orangefs.rst | 1 .. SPDX-License-Identifier: GPL-2.0 7 OrangeFS is an LGPL userspace scale-out parallel storage system. It is ideal 44 Running ORANGEFS On a Single Server 51 On Fedora, install orangefs and orangefs-server:: 53 dnf -y install orangefs orangefs-server 55 There is an example server configuration file in 64 pvfs2-client-core. 68 pvfs2-server -f /etc/orangefs/orangefs.conf 70 Start the server:: 72 systemctl start orangefs-server [all …]
|
| /Documentation/admin-guide/cifs/ |
| D | todo.rst | 21 are currently the only two server side copy mechanisms supported) 35 roundtrips to the server and improve performance. Various cases 52 i) Add support for tree connect contexts (see MS-SMB2) a new SMB3.1.1 protocol 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 62 directly from user space) Add tools to make setting various non-POSIX 64 in smb-info tool). 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. [all …]
|
| D | authors.rst | 6 --------------- 15 Jeremy Allison of the Samba team has done invaluable work in adding the server 16 side of the original CIFS Unix extensions and reviewing and implementing 17 portions of the newer CIFS POSIX extensions into the Samba 3 file server. Thank 19 for proving years ago that very good smb/cifs clients could be done on Unix-like 27 ------------------ 29 - Zwane Mwaikambo 30 - Andi Kleen 31 - Amrut Joshi 32 - Shobhit Dayal [all …]
|
| D | usage.rst | 18 MS-SMB2 (for detailed SMB2/SMB3/SMB3.1.1 protocol specification) 36 (e.g. /usr/src/linux-2.5.73) 48 the modules directory e.g. /lib/modules/6.3.0-060300-generic/kernel/fs/smb/client/cifs.ko). 57 required, mount.cifs is recommended. Most distros include a ``cifs-utils`` 63 found at cifs-utils.git on git.samba.org 66 and maximum number of simultaneous requests to one server can be configured. 100 //server/usersharename /mnt/username cifs user 0 0 122 mounts, unless umount is invoked with -i (which will avoid invoking a umount 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 [all …]
|
| /Documentation/netlink/specs/ |
| D | mptcp_pm.yaml | 1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 4 protocol: genetlink-legacy 7 c-family-name: mptcp-pm-name 8 c-version-name: mptcp-pm-ver 9 max-by-define: true 10 kernel-policy: per-op 11 cmd-cnt-name: --mptcp-pm-cmd-after-last 14 - 16 name: event-type 17 enum-name: mptcp-event-type [all …]
|
| /Documentation/filesystems/smb/ |
| D | ksmbd.rst | 1 .. SPDX-License-Identifier: GPL-2.0 4 KSMBD - SMB3 Kernel Server 7 KSMBD is a linux kernel server which implements SMB3 protocol in kernel space 23 --------------------- 25 When the server daemon is started, It starts up a forker thread 29 communication channel between the client and the server. It allows for parallel 36 as workitems and to be executed in the handlers of the ksmbd-io kworker threads. 44 for each command which is further queued to be handled by ksmbd-io kworkers. 50 -------------------------------- 58 dozen) that are most important for file server from NetShareEnum and [all …]
|
| /Documentation/gpu/ |
| D | vgaarbiter.rst | 7 implemented on PCI will typically have the same "hard-decoded" addresses as 8 they did on ISA. For more details see "PCI Bus Binding to IEEE Std 1275-1994 12 The Resource Access Control (RAC) module inside the X server [0] existed for 14 than one legacy device co-exists on the same machine. But the problem happens 16 (e.g. two server in parallel). Their address assignments conflict. Moreover, 17 ideally, being a userspace application, it is not the role of the X server to 18 control bus resources. Therefore an arbitration scheme outside of the X server 23 --------------------------- 51 unplugged, we get "invalid" then for card_ID and an -ENODEV 63 non-blocking acquire locks on target (returns EBUSY if [all …]
|
| /Documentation/admin-guide/mm/ |
| D | multigen_lru.rst | 1 .. SPDX-License-Identifier: GPL-2.0 4 Multi-Gen LRU 6 The multi-gen LRU is an alternative LRU implementation that optimizes 26 ----------- 30 unless some of them have unforeseen side effects. Writing to 38 0x0001 The main switch for the multi-gen LRU. 42 disabled, the multi-gen LRU will suffer a minor performance 46 0x0004 Clearing the accessed bit in non-leaf page table entries as 49 disabled, the multi-gen LRU will suffer a negligible 65 -------------------- [all …]
|
| /Documentation/driver-api/usb/ |
| D | gadget.rst | 11 This document presents a Linux-USB "Gadget" kernel mode API, for use 17 - Supports USB 2.0, for high speed devices which can stream data at 20 - Handles devices with dozens of endpoints just as well as ones with 21 just two fixed-function ones. Gadget drivers can be written so 24 - Flexible enough to expose more complex USB device capabilities such 28 - USB "On-The-Go" (OTG) support, in conjunction with updates to the 29 Linux-USB host side. 31 - Sharing data structures and API models with the Linux-USB host side 32 API. This helps the OTG support, and looks forward to more-symmetric 34 side drivers). [all …]
|
| /Documentation/fb/ |
| D | framebuffer.rst | 9 --------------- 13 software to access the graphics hardware through a well-defined interface, so 14 the software doesn't need to know anything about the low-level (hardware 22 -------------------------- 39 /dev/fb0current -> fb0 40 /dev/fb1current -> fb1 50 graphics card in addition to the built-in hardware. The corresponding frame 53 Application software that uses the frame buffer device (e.g. the X server) will 65 After this the X server will use the second frame buffer. 69 -------------------------------- [all …]
|
| /Documentation/misc-devices/ |
| D | ibmvmc.rst | 1 .. SPDX-License-Identifier: GPL-2.0+ 21 https://openpowerfoundation.org/wp-content/uploads/2016/05/LoPAPR_DRAFT_v11_24March2016_cmt1.pdf 27 Console (HMC) - based system management. 30 on an appliance server named the Hardware Management Console (HMC), 31 packaged as an external tower or rack-mounted personal computer. In a 33 processor-based systems. 36 ---------------------- 44 POWER8 or newer processor-based server that is virtualized by PowerVM. 57 - Logical Partitioning Configuration 58 - Start, and stop actions for individual partitions [all …]
|
| /Documentation/virt/hyperv/ |
| D | vmbus.rst | 1 .. SPDX-License-Identifier: GPL-2.0 5 VMBus is a software construct provided by Hyper-V to guest VMs. It 7 devices that Hyper-V presents to guest VMs. The control path is 11 and the synthetic device implementation that is part of Hyper-V, and 12 signaling primitives to allow Hyper-V and the guest to interrupt 17 establishes the VMBus control path with the Hyper-V host, then 21 Most synthetic devices offered by Hyper-V have a corresponding Linux 29 * PCI device pass-thru 34 * Key/Value Pair (KVP) exchange with Hyper-V 35 * Hyper-V online backup (a.k.a. VSS) [all …]
|
123