Searched full:clients (Results 1 – 25 of 142) sorted by relevance
123456
| /Documentation/filesystems/nfs/ |
| D | client-identifier.rst | 41 leases. When the server restarts and clients attempt to recover
43 clients that held state before the server restarted and clients
92 circumstances where clients can interfere with each other. This is
95 If distinct clients present the same "co_ownerid" string and use
97 unable to tell that the clients are not the same. Each distinct
102 If distinct clients present the same "co_ownerid" string and use
104 to operate normally but reject subsequent clients with the same
117 to other clients in the meantime. This is referred to as "lock
134 - NFS-root (diskless) clients, where the local DHCP server (or
142 - Clients across multiple administrative domains that access a
|
| /Documentation/userspace-api/ |
| D | tee.rst | 30 There are two classes of clients, normal clients and supplicants. The latter is
35 Much of the communication between clients and the TEE is opaque to the
37 clients, forward them to the TEE and send back the results. In the case of
|
| /Documentation/admin-guide/nfs/ |
| D | pnfs-scsi-server.rst | 9 also hands out layouts to the clients so that they can directly access the
14 file system must sit on a SCSI LUN that is accessible to the clients in
16 exported LUN, striping or concatenation of LUNs on the MDS and clients
|
| D | pnfs-block-server.rst | 8 to the clients to directly access the underlying block devices that are
14 to the clients in addition to the MDS. As of now the file system needs to
16 volumes on the MDS and clients is not supported yet.
|
| D | nfs-client.rst | 25 NFSv4 requires clients to identify themselves to servers with a unique
41 nfs.nfs4_unique_id can help prevent collisions with other clients.
44 anything that is believed to be unique across all NFS clients. An
57 This uniquifier string will be the same for all NFS clients running in
|
| /Documentation/gpu/ |
| D | tegra.rst | 7 buffer provided directly by the CPU, to its clients via channels. Software,
30 The various host1x clients need to be bound together into a logical device in
35 tree for matching device nodes, adding the required clients to a list. Drivers
36 for individual clients register with the infrastructure as well and are added
39 Once all clients are available, the infrastructure will initialize the logical
41 the subsystem and in turn initialize each of its clients.
43 Similarly, when one of the clients is unregistered, the infrastructure will
45 the subsystem specific bits are torn down and the clients destroyed in turn.
|
| D | drm-uapi.rst | 137 clients no longer require running compositors or graphics servers to
138 make use of a GPU. But the DRM API required unprivileged clients to
140 step and to grant clients GPU access without authenticating, render
141 nodes were introduced. Render nodes solely serve render clients, that
146 clients together with the legacy drmAuth authentication procedure.
154 nodes are designed to avoid the buffer-leaks, which occur if clients
158 clients can use them. Driver authors must be careful not to allow any
163 authenticates clients on the privileged primary/legacy node is no longer
165 granted GPU access. Communication between clients (or servers) is done
167 clients must not use the insecure FLINK interface.
[all …]
|
| D | drm-client.rst | 2 Kernel clients
|
| /Documentation/virt/acrn/ |
| D | io-request.rst | 23 2. I/O clients
27 GPA falls in a certain range. Multiple I/O clients can be associated with each
30 any other clients. The ACRN userspace acts as the default client for each User
34 I/O requests and I/O clients.
54 || | | | I/O clients | | | |
93 registered clients based on the address of the I/O accesses, updates
|
| /Documentation/devicetree/bindings/dma/ |
| D | moxa,moxart-dma.txt | 23 Clients:
25 DMA clients connected to the MOXA ART DMA controller must use the format
|
| D | atmel-xdma.txt | 29 * DMA clients
30 DMA clients connected to the Atmel XDMA controller must use the format
|
| D | mpc512x-dma.txt | 29 DMA clients must use the format described in dma/dma.txt file.
|
| /Documentation/devicetree/bindings/cache/ |
| D | qcom,llcc.yaml | 14 that can be shared by multiple clients. Clients here are different cores in the
15 SoC, the idea is to minimize the local caches at the clients and migrate to
17 which are assigned to clients. Clients can query the slice details, activate
|
| /Documentation/i2c/ |
| D | dma-considerations.rst | 21 Clients chapter
24 For clients, if you use a DMA safe buffer in i2c_msg, set the I2C_M_DMA_SAFE
29 more and more clients and host drivers is the planned way forward. Note also
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | nvidia,tegra20-mc.yaml | 17 and returns response data to the various clients. The Memory Controller
19 performance among the various clients.
|
| /Documentation/ABI/stable/ |
| D | sysfs-bus-mhi | 10 Users: Any userspace application or clients interested in device info.
21 Users: Any userspace application or clients interested in device info.
|
| /Documentation/translations/sp_SP/process/ |
| D | index.rst | 18 email-clients
|
| /Documentation/devicetree/bindings/devfreq/ |
| D | nvidia,tegra30-actmon.yaml | 18 from the monitored clients.
59 memory clients, see MEMORY CONTROLLER and ACTIVITY MONITOR sections.
|
| /Documentation/driver-api/surface_aggregator/ |
| D | index.rst | 12 clients/index
|
| /Documentation/sound/designs/ |
| D | midi-2.0.rst | 44 clients, and the events are converted transparently.
177 sequencer event as was. Meanwhile, UMP MIDI 1.0 and 2.0 clients send
191 The type of each client can be seen in `/proc/asound/seq/clients`.
194 % cat /proc/asound/seq/clients
196 cur clients : 3
213 Here you can find two types of kernel clients, "Legacy" for client 14,
236 When clients are connected between different MIDI versions, the events
294 UMP EP info and the corresponding sequencer clients as well.
340 * The event conversion of ALSA sequencer clients can be suppressed the
362 * Two new ioctls are added for UMP-capable clients:
|
| /Documentation/ABI/removed/ |
| D | raw1394 | 8 of abstraction that required userspace clients to duplicate much
|
| /Documentation/driver-api/pci/ |
| D | p2pdma.rst | 41 clients and providers.
100 that's compatible with all clients using :c:func:`pci_p2pmem_find()`.
101 If more than one provider is supported, the one nearest to all the clients will
|
| /Documentation/process/ |
| D | email-clients.rst | 3 Email clients info for Linux
10 email clients. The man page for this is quite good. On the receiving
31 listing recommended email clients should you not already have a preference.
33 Email clients that are used for Linux kernel patches should send the
43 Email clients should not modify the character set encoding of the text.
48 Email clients should generate and maintain "References:" or "In-Reply-To:"
|
| /Documentation/filesystems/smb/ |
| D | ksmbd.rst | 27 for listening to SMB requests. Whenever new clients make a request, the Forker
30 processing of SMB requests(commands) from clients as well as allowing for new
31 clients to make new connections. Each instance is named ksmbd/1~n(port number)
32 to indicate connected clients. Depending on the SMB request types, each new
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,pbs.yaml | 14 supports triggering power up and power down sequences for clients
|
123456