Searched full:received (Results 1 – 25 of 317) sorted by relevance
12345678910>>...13
| /Documentation/networking/ |
| D | altera_tse.txt | 78 received, the DMA logic generates an interrupt. The driver handles a receive
141 received. This count does not include any error packets such as CRC errors,
147 is received.
152 received.
160 successfully received by the controller.
168 received by the network controller.
171 a count of the number of packets received containing errors that prevented the
178 statistic is a count of the number of packets received that were not addressed
182 statistic is a count of the number of packets received that were addressed to
186 statistic is a count of the number of packets received that were addressed to
[all …]
|
| D | tls.rst | 104 be received before decryption can happen.
111 Received data is decrypted directly in to the user buffer if it is
116 ``EINVAL`` is returned if the TLS version in the received message does not
119 ``EMSGSIZE`` is returned if the received message is too big.
169 returned if a control message is received. Data messages may be
170 received without a cmsg buffer set.
|
| D | rxrpc.txt | 150 A hard-ACK indicates to the far side that all the data received to a point
151 has been received and processed; a soft-ACK indicates that the data has
152 been received but may yet be discarded and re-requested. The sender may
159 received and the final hard-ACK on the last packet of the reply has
203 (*) If an ICMP error is received, all calls affected by that error will be
213 followed by the reply being received with one or more recvmsgs.
230 (*) Once the application has received the last message associated with a call,
235 (*) In the server, a request is received with one or more recvmsgs, then the
237 is received with a last recvmsg.
266 (*) When the kernel has received and set up an incoming call, it sends a
[all …]
|
| D | lapb-module.txt | 22 received and transmitted data, however it is beyond the scope of this
185 Queue data with the LAPB module which has been received from the device. It
226 LAPB_TIMEDOUT No response was received in N2 tries from the remote
241 LAPB_TIMEDOUT No response was received in N2 tries from the remote
247 This is called by the LAPB module when data has been received from the
|
| D | snmp_counter.rst | 19 The number of packets received by the IP layer. It gets increasing at the
62 These 4 counters calculate how many packets received per ECN
257 The number of packets received by the TCP layer. As mentioned in
258 RFC1213, it includes the packets received in error, such as checksum
301 When packets are received by the TCP layer and are not be read by the
430 - Unexpected TCP flags/window values/header lengths are received
629 detect reorder: (1) DSACK is received by the sender. It means the
633 the sender has received SACKs for packet 2 and 5, now the sender
686 duplicate packet is received.
691 duplicate packet is received.
[all …]
|
| D | strparser.txt | 18 received on the socket.
111 0 : indicates more data must be received to parse the message
143 rcv_msg is called when a full message has been received and
146 received in rcv_msg (see strp_pause above). This callback
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-net-statistics | 14 Indicates the number of multicast packets received by this
22 Indicates the number of bytes received by this network device.
31 Indicates the number of compressed packets received by this
40 Indicates the number of packets received with a CRC (FCS) error
49 Indicates the number of packets received by the network device
68 Indicates the number of received frames with error, such as
78 Indicates the number of received error packet with a length
87 Indicates the number of received packets that have been missed
96 Indicates the number of received packets that are oversized
106 Indicates the total number of good packets received by this
|
| D | sysfs-class-uwb_rc | 16 If no beacons are received from a device for at least
109 this device was received.
142 (SNR) of all packets received from this device in dB.
151 Received Signal Strength Indication - the strength of
152 the received signal in dB. LQE is a more useful
|
| D | sysfs-devices-platform-ipmi | 133 events: (RO) Number of IPMI events received from
153 received.
207 alerts: (RO) Number of alerts received.
216 received.
219 received.
221 events: (RO) Number of received events.
|
| /Documentation/isdn/ |
| D | avmb1.rst | 129 capi messages received without DATA_B3_IND
131 capi DATA_B3_IND received
150 capi messages received without DATA_B3_IND
152 capi DATA_B3_IND received
165 capi messages received without DATA_B3_IND
167 capi DATA_B3_IND received
188 capi messages received without DATA_B3_IND
190 capi DATA_B3_IND received
|
| /Documentation/media/uapi/cec/ |
| D | cec-pin-error-inj.rst | 52 # <op>[,<mode>] rx-add-byte add a spurious byte to the received CEC message
53 # <op>[,<mode>] rx-remove-byte remove the last byte from the received CEC message
106 received or transmitted message, ``always`` to always trigger the error
110 So '``any rx-nack``' will NACK the next received CEC message,
111 '``any,always rx-nack``' will NACK all received CEC messages and
113 received and do that only for every other received message.
168 otherwise the opcode hasn't been received yet. This tests if the
175 Add a spurious 0x55 byte to the received CEC message, provided
180 Remove the last byte from the received CEC message, provided it
187 As soon as a start bit has been received the CEC adapter will switch
[all …]
|
| D | cec-ioc-receive.rst | 47 If the file descriptor is in non-blocking mode and there are no received
53 A received message can be:
55 1. a message received from another CEC device (the ``sequence`` field will
76 checked against the received messages to find the corresponding transmit
110 - Timestamp in ns of when the last byte of the message was received.
122 for a message to be received before timing out. If it is set to 0,
132 allows the application to associate the received message with the original
141 this message was received, not transmitted.
166 synchronized with the contents of the received message.
169 - The status bits of the received message. See
[all …]
|
| /Documentation/infiniband/ |
| D | user_mad.rst | 42 MADs are received using read(). The receive side now supports
46 If the buffer passed is not large enough to hold the received
77 fields will be filled in with information on the received MAD. For
81 to ETIMEDOUT. Otherwise when a MAD has been successfully received,
122 index of received MADs. A new layout for struct ib_user_mad_hdr
|
| /Documentation/devicetree/bindings/pci/ |
| D | xilinx-nwl-pcie.txt | 18 "msi1, msi0": interrupt asserted when an MSI is received
19 "intx": interrupt asserted when a legacy interrupt is received
20 "misc": interrupt asserted when miscellaneous interrupt is received
|
| /Documentation/media/v4l-drivers/ |
| D | si476x.rst | 76 0x02 received Number of received RDS blocks
107 RSQ(Received Signal Quality)
121 0x02 snrhint 0 - received signal's SNR has not
123 1 - received signal's SNR has
159 RSQ(Received Signal Quality) for primary tuner only. Layout is as
|
| /Documentation/devicetree/bindings/iio/proximity/ |
| D | devantech-srf04.yaml | 17 until it is received once again
47 out and reset when the first echo is received.
|
| /Documentation/hid/ |
| D | hidraw.rst | 7 received are not parsed by the HID parser, but are sent to and received from
17 descriptors. Because hiddev parses reports which are sent and received
43 read() will read a queued report received from the HID device. On USB
|
| /Documentation/virt/kvm/ |
| D | halt-polling.txt | 44 During polling if a wakeup source is received within the halt polling interval,
46 received during the polling interval (and thus schedule is invoked) there are
54 will be received while the host is polling and the latency benefits will be
55 received. The polling interval is grown in the function grow_halt_poll_ns() and
72 invoked and a wakeup source received (irrespective of
|
| /Documentation/devicetree/bindings/display/bridge/ |
| D | thine,thc63lvd1024.txt | 32 mode, all pixels are received on port@0, and port@1 shall not contain any
33 endpoint. In dual-link mode, even-numbered pixels are received on port@0 and
|
| /Documentation/networking/device_drivers/freescale/ |
| D | dpaa.txt | 153 different traffic flows received by one interface to be processed by different
184 and L4 source and destination ports, in present in the received frame.
185 When RSS is disabled, all traffic received by a certain interface is
186 received on the default Rx frame queue. The default DPAA Rx frame
187 queues are configured to put the received traffic into a pool channel
192 is that only one CPU at a time can service the traffic received by a
|
| /Documentation/devicetree/bindings/sound/ |
| D | cs35l35.txt | 27 0 = Data Packet received on Left I2S Channel
28 1 = Data Packet received on Right I2S Channel
31 0 = Data Packet received on Left I2S Channel
32 1 = Data Packet received on Right I2S Channel
|
| /Documentation/ |
| D | IRQ-affinity.txt | 35 6029 packets transmitted, 6027 packets received, 0% packet loss
54 2779 packets transmitted, 2777 packets received, 0% packet loss
|
| /Documentation/ABI/removed/ |
| D | dv1394 | 7 could be received by read() or transmitted by write(). A few
|
| /Documentation/admin-guide/wimax/ |
| D | i2400m.rst | 231 * RX-buffers: total RX buffers received, accumulated RX buffer size
232 in bytes, min size received, max size received
234 Thus, to find the average buffer size received, divide accumulated
247 5.2.3. Tracing messages received from user space
250 To echo messages received from user space into the trace pipe that the
|
| /Documentation/networking/device_drivers/amazon/ |
| D | ena.txt | 148 - Increased process-level parallelism when handling received packets.
197 bytes and packets received between interrupt unmasking and interrupt
199 range of received bytes/packets into 5 levels and assigns interrupt
213 The driver-allocated SKB for frames received from Rx handling using
253 function delivered in the Rx CQ descriptor is set in the received
291 - When a packet is received from the ENA device.
|
12345678910>>...13