| /Documentation/networking/ |
| D | snmp_counter.rst | 275 it excludes the retransmitted packets. But it includes the SYN, ACK
296 It means the TCP layer receives a SYN, replies a SYN+ACK, come into
329 TCPSynRetrans: number of SYN and SYN/ACK retransmits to break down
357 half open queue, TCP stack will send SYN+ACK on an exponential backoff
358 timer, after client replies ACK, TCP stack checks whether the accept
361 time client replies ACK, this socket will get another chance to move
431 or pure receivers (this means either the sequence number or the ack
438 good. Kernel would also come into slow path if the "Delayed ack" is
439 used, because when using "Delayed ack", the data is sent in both
448 If a packet set ACK flag and has no data, it is a pure ACK packet, if
[all …]
|
| D | proc_net_tcp.rst | 38 | | | | | | | |-------> (ack.quick<<1)|ack.pingpong
40 | | | | | | (delayed ACK control data)
53 2 another timer (e.g. delayed ack or keepalive) is pending
|
| D | rds.rst | 208 ACK_REQUIRED receiver must ack this packet
224 ACK and retransmit handling
227 to ack messages that have been received. The problem is that IB
228 hardware generates an ack message before it has DMAed the message
230 disabled for any reason between when it sends the ack and before
234 Sending an ack immediately would allow the sender to free the sent
237 packets. Ack-only packets are reduced by only allowing one to be
359 - piggybacks ack
379 - note if ack is required
|
| D | rxrpc.rst | 146 (#) Calls use ACK packets to handle reliability. Data packets are also
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
153 not discard any transmittable packets until they've been hard-ACK'd.
155 (#) Reception of a reply data packet implicitly hard-ACK's all the data
159 received and the final hard-ACK on the last packet of the reply has
196 (#) ACK'ing is handled by the protocol driver automatically, including ping
235 the reply is transmitted with one or more sendmsgs, and then the final ACK
333 RXRPC_ACK -rt n/a Final ACK received
364 This is delivered to a server application to indicate that the final ACK
[all …]
|
| /Documentation/driver-api/md/ |
| D | md-cluster.rst | 62 managed through three locks: "token", "message", and "ack", together
141 3.2.3 ack
151 1. receive status - all nodes have concurrent-reader lock on "ack"::
154 "ack":CR "ack":CR "ack":CR
160 "token":EX "ack":CR "ack":CR
162 "ack":CR
172 sender try to get EX of "ack"
178 [ triggered by bast of "ack" ]
183 receiver releases "ack"
189 "ack":EX
[all …]
|
| /Documentation/devicetree/bindings/net/ |
| D | qcom,bam-dmux.yaml | 38 - const: pc-ack
51 - const: pc-ack
84 interrupt-names = "pc", "pc-ack";
87 qcom,smem-state-names = "pc", "pc-ack";
|
| /Documentation/devicetree/bindings/dma/stm32/ |
| D | st,stm32-dma.yaml | 44 0x0: Use standard DMA ACK management, where ACK signal is maintained
46 0x1: Use alternative DMA ACK management, where ACK de-assertion does
47 not wait for the de-assertion of the REQuest, ACK is only managed
|
| /Documentation/translations/ja_JP/ |
| D | stable_kernel_rules.txt | 55 - 送信者はパッチがキューに受け付けられた際には ACK を、却下された場合
70 - レビュー委員会は 48時間の間に ACK か NAK を出す。
74 - レビューサイクルの最後に、ACK を受けたパッチは最新の -stable リリー
|
| /Documentation/i2c/ |
| D | slave-interface.rst | 80 always ack the address phase. If 'ret' is zero, backend initialization or
102 is zero, the bus driver should ack this byte. If 'ret' is an errno, then the byte
165 About ACK/NACK
168 It is good behaviour to always ACK the address phase, so the master knows if a
170 state being busy is troublesome. SMBus demands to always ACK the address phase,
172 automatically ACK when detecting their slave addresses, so there is no option
176 Currently, there is no slave event to report if the master did ACK or NACK a
|
| D | gpio-fault-injection.rst | 60 it will stop at the ACK phase after the address of the client has been
61 transmitted. Because the device will ACK its presence, this results in SDA
73 The injector will again stop at one ACK phase, so the device will keep SDA low
78 b) after the address byte, a 0x00 byte will be transferred. Then, stop at ACK.
|
| /Documentation/devicetree/bindings/remoteproc/ |
| D | qcom,sc7280-adsp-pil.yaml | 45 - const: stop-ack
46 - const: shutdown-ack
164 "handover", "stop-ack", "shutdown-ack";
|
| D | qcom,sc7280-wpss-pil.yaml | 41 - const: stop-ack
42 - const: shutdown-ack
175 "stop-ack", "shutdown-ack";
|
| D | qcom,pas-common.yaml | 44 - const: stop-ack
45 - const: shutdown-ack
|
| D | qcom,sc7180-mss-pil.yaml | 51 - const: stop-ack
52 - const: shutdown-ack
211 "stop-ack", "shutdown-ack";
|
| D | qcom,sdx55-pas.yaml | 92 "stop-ack", "shutdown-ack";
|
| D | qcom,sc7280-mss-pil.yaml | 55 - const: stop-ack
56 - const: shutdown-ack
231 "stop-ack", "shutdown-ack";
|
| D | qcom,sc8280xp-pas.yaml | 124 "handover", "stop-ack", "shutdown-ack";
|
| D | st,stm32-rproc.yaml | 72 - from remote to local = send message ack
79 - from local to remote, where ACK from the remote means that it is
85 - from local to remote, where ACK from the remote means that communication
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | apple,aic2.yaml | 20 - Automatic masking on event delivery (auto-ack)
22 - Automatic prioritization (single event/ack register per CPU, lower IRQs =
24 - Automatic masking on ack
|
| D | apple,aic.yaml | 22 - Automatic masking on event delivery (auto-ack)
26 - Automatic prioritization (single event/ack register per CPU, lower IRQs =
28 - Automatic masking on ack
|
| /Documentation/input/devices/ |
| D | walkera0701.rst | 31 / O 4 3 O \ pin 3 (GND) LED ________________ 10 ACK
55 Driver use interrupt from parport ACK input bit to measure pulse length
98 (Warning, pulses on ACK are inverted by transistor, irq is raised up on sync
|
| /Documentation/driver-api/surface_aggregator/ |
| D | ssh.rst | 10 .. |ACK| replace:: ``ACK`` substdef
119 * - |ACK|
131 Both |NAK|- and |ACK|-type frames are used to control flow of messages and
144 the frame by responding with a message containing an |ACK|-type frame with
146 the |ACK| frame specifies the |DATA| frame to be acknowledged. In case of an
158 used to associate an ``ACK`` with its ``DATA_SEQ``-type frame, but not
169 indicates a |DATA_SEQ|-type frame, ``FRAME(A)`` an ``ACK``-type frame,
334 the EC is sent again, e.g. due to the host not receiving an |ACK|, the EC
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,rpm.yaml | 35 - const: ack
76 interrupt-names = "ack", "err", "wakeup";
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | arm,mhuv3.yaml | 157 - pattern: '^pbx-dbch-xfer-ack-[0-9]+$'
158 description: PBX Doorbell Channel <N> Transfer Ack interrupt
159 - pattern: '^pbx-ffch-xfer-ack-[0-9]+$'
160 description: PBX FIFO Channel <N> Transfer Ack interrupt
208 interrupt-names = "combined", "pbx-dbch-xfer-ack-1",
|
| /Documentation/driver-api/ |
| D | connector.rst | 49 __u32 ack;
71 msg->seq and msg->ack are used to determine message genealogy. When
105 cn_msg [main connector's message header] contains u32 seq and u32 ack
|