Searched full:connection (Results 1 – 25 of 323) sorted by relevance
12345678910>>...13
| /Documentation/ABI/testing/ |
| D | sysfs-devices-physical_location | 6 the device connection point with respect to the system's
14 device connection point resides on.
20 Describes vertical position of the device connection point on
27 Describes horizontal position of the device connection point on
34 "Yes" if the device connection point resides in a docking
41 "Yes" if the device connection point resides on the lid of
|
| D | sysfs-platform-usbip-vudc | 33 connection peer. It is done by writing to this
35 associated with a connection to remote peer who
37 close the connection by writing -1 instead of
|
| D | sysfs-bus-pci-drivers-ehci_hcd | 10 high-speed device is plugged in, the connection is routed
12 is plugged in, the connection is routed to the companion
17 connection to be routed to the companion controller.
|
| /Documentation/networking/ |
| D | ipvs-sysctl.rst | 39 connection will be delivered to the same real server that was
40 servicing the previous connection.
44 the connection is in TIME_WAIT state (which is only possible if
56 If set, maintain connection tracking entries for
61 that make use of connection tracking. It is a performance
65 will have connection tracking entries regardless of this setting.
86 - 7 - connection new/expire, lookup and synchronization
104 connection hash table, just in order to collect back some
164 connection immediately when a packet arrives and its
166 will be notified that the connection is closed. This is
[all …]
|
| D | nf_conntrack-sysctl.rst | 14 Enable connection tracking flow accounting. 64-bit byte and packet
30 considered for connection tracking.
40 If this option is enabled, the connection tracking code will
41 provide userspace with connection tracking events via ctnetlink.
96 Maximum number of allowed connection tracking entries. This value is set
98 Note that connection tracking entries are added to the table twice -- once
164 Enable connection tracking flow timestamping.
225 Once aged, the connection is returned to nf conntrack.
232 Once aged, the connection is returned to nf conntrack.
|
| D | rds.rst | 20 reliable connection between any two nodes in the cluster. This allows
23 to N*N if you use a connection-oriented socket transport like TCP.
34 the end point of a connection. All socket operations that involve
40 reliable IB connection; the IP address is used exclusively to
101 transparently establish the underlying reliable connection
213 indicate to other end of connection that
246 eliminates the need for hardware retries on the connection.
283 loopback, stats, usermem pinning, and the connection state machine.
296 This is then queued for the individual connection and sent by the
297 connection's transport.
[all …]
|
| D | tcp_ao.rst | 34 |TCP connection | | |
68 >> The IDs of MKTs MUST NOT overlap where their TCP connection
71 Q: Can Master Key Tuple (MKT) for an active connection be removed?
75 It is presumed that an MKT affecting a particular connection cannot
76 be destroyed during an active connection -- or, equivalently, that
77 its parameters are copied to an area local to the connection (i.e.,
81 to not remove it for an active connection? (As it can be still in use
109 may yet not have the new key - the TCP connection may just break.
112 Q: What happens when a packet is received on a new connection with no known
119 connection. Find the matching MKT for this segment, using the segment's
[all …]
|
| D | tls-offload.rst | 10 Linux kernel provides TLS connection offload infrastructure. Once a TCP
11 connection is in ``ESTABLISHED`` state user space can enable the TLS Upper
12 Layer Protocol (ULP) and install the cryptographic connection state.
36 offload opt-in or opt-out on per-connection basis is not currently supported.
79 When TLS cryptographic connection state is installed on a ``ktls`` socket
83 fails the connection is handled entirely in software using the same mechanism
98 to retrieve the connection 5-tuple and socket family (IPv4 vs IPv6).
118 before installing the connection state in the kernel.
129 At the minimum the device maintains the following state for each connection, in
163 a connection identifier (note that a 5-tuple lookup is insufficient to identify
[all …]
|
| D | dccp.rst | 20 Datagram Congestion Control Protocol (DCCP) is an unreliable, connection
54 a policy ID as argument and can only be set before the connection (i.e. changes
55 during an established connection are not supported). Currently, two policies are
106 timewait state when closing the connection (RFC 4340, 8.3). The usual case is
140 On unidirectional connections it is useful to close the unused half-connection
150 The number of active connection initiation retries (the number of
168 Default CCID for the sender-receiver half-connection. Depending on the
172 Default CCID for the receiver-sender half-connection; see tx_ccid.
|
| /Documentation/networking/device_drivers/ethernet/intel/ |
| D | e1000e.rst | 4 Linux Driver for Intel(R) Ethernet Network Connection
130 controller is automatically reset, restoring the network connection. To
286 - Intel(R) 82578DM Gigabit Network Connection
287 - Intel(R) 82577LM Gigabit Network Connection
292 - Intel(R) PRO/1000 PM Network Connection
293 - Intel(R) 82562G 10/100 Network Connection
294 - Intel(R) 82562G-2 10/100 Network Connection
295 - Intel(R) 82562GT 10/100 Network Connection
296 - Intel(R) 82562GT-2 10/100 Network Connection
297 - Intel(R) 82562V 10/100 Network Connection
[all …]
|
| /Documentation/userspace-api/media/mediactl/ |
| D | media-controller-model.rst | 24 - A **pad** is a data connection endpoint through which an entity can
30 - A **data link** is a point-to-point oriented connection between two
35 connection between a Linux Kernel interface and an entity.
37 - An **ancillary link** is a point-to-point connection denoting that two
|
| /Documentation/admin-guide/blockdev/drbd/ |
| D | peer-states-8.dot | 4 Primary -> Unknown [ label = "connection lost" ]
5 Secondary -> Unknown [ label = "connection lost" ]
|
| /Documentation/devicetree/bindings/sound/ |
| D | omap-twl4030.txt | 13 Each entry is a pair of strings, the first being the connection's sink,
14 the second being the connection's source.
15 If the routing is not provided all possible connection will be available
|
| D | mxs-audio-sgtl5000.txt | 10 connection's sink, the second being the connection's
|
| D | sound-card-common.yaml | 17 pair of strings, the first being the connection's sink, the second
18 being the connection's source.
|
| /Documentation/driver-api/mei/ |
| D | mei.rst | 20 upon connection.
106 ENOTTY No such client (i.e. wrong GUID) or connection is not allowed.
108 ENODEV Device or Connection is not initialized or ready.
111 EBUSY Connection Already Open
143 ENOTTY No such client (i.e. wrong GUID) or connection is not allowed.
145 ENODEV Device or Connection is not initialized or ready.
148 EBUSY Connection Already Open
|
| /Documentation/devicetree/bindings/arm/ |
| D | arm,embedded-trace-extension.yaml | 22 with any optional connection graph as per the coresight bindings.
45 description: Output connection from the ETE to legacy CoreSight Trace bus.
68 out-ports { /* legacy coresight connection */
|
| D | arm,coresight-cti.yaml | 39 When CTI trigger connection information is unavailable then a minimal driver
43 connection. Any user / client application will require additional information
115 registered then the node name will be stored as the connection name for
117 not registered then the node name will remain the connection name and
136 The connection may have both input and output triggers, or only one or the
145 Handle to cpu this trigger connection is associated with.
153 then the node name will be stored as the connection name for later
155 not registered then the node name will remain the connection name
203 Defines a connection name that will be displayed, if the cpu or
204 arm,cs-dev-assoc properties are not being used in this connection.
|
| /Documentation/devicetree/bindings/net/nfc/ |
| D | marvell,nci.yaml | 39 For I2C type of connection. Specifies that the chip read event shall be
45 For I2C type of connection. Specifies that the chip read event shall be
51 For UART type of connection. Specifies that the chip needs specific break
57 For UART type of connection. Specifies that the chip is using RTS/CTS.
|
| /Documentation/sound/hd-audio/ |
| D | dp-mst.rst | 32 Connection list
34 DP MST reuses connection list code. The code can be reused because
35 device entries on the same pin have the same connection list.
37 This means DP MST gets the device entry connection list without the
|
| /Documentation/arch/powerpc/ |
| D | hvcs.rst | 27 5. Connection:
208 5. Connection
273 and discards that data when a connection between a vty-server and a vty has
277 connection was severed to fetch the data from firmware before the fetch is
287 the vty-server and vty connection before the target vty has had a chance to
296 outlined below, on the other hand the initial vty-server connection to a
298 connection is never required.
300 In order to terminate the connection between a vty-server and vty the
302 Reading this attribute reveals the current connection state of the
304 vty. A one indicates that a connection is active.
[all …]
|
| /Documentation/devicetree/bindings/regulator/ |
| D | rohm,bd71847-regulator.yaml | 104 # by adding external connection where some other regulator output is
110 # So we allow describing this external connection from DT and scale the
111 # voltages accordingly. This is what the connection should look like:
138 Feedback-pin has pull-up connection to adjust voltage range. This is
143 Feedback-pin has pull-up connection to adjust voltage range. This is
148 Feedback-pin has pull-up connection to adjust voltage range. This is
|
| D | rohm,bd71837-regulator.yaml | 109 # by adding external connection where some other regulator output is
115 # So we allow describing this external connection from DT and scale the
116 # voltages accordingly. This is what the connection should look like:
143 Feedback-pin has pull-up connection to adjust voltage range. This is
148 Feedback-pin has pull-up connection to adjust voltage range. This is
153 Feedback-pin has pull-up connection to adjust voltage range. This is
|
| /Documentation/devicetree/bindings/ata/ |
| D | cavium-compact-flash.txt | 15 - cavium,bus-width: The width of the connection to the CF devices. Valid
18 - cavium,true-ide: Optional, if present the CF connection is in True IDE mode.
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | cirrus,lochnagar.yaml | 14 Smart CODEC and Amp devices. It allows the connection of most Cirrus
15 Logic devices on mini-cards, as well as allowing connection of various
|
12345678910>>...13