| /linux/drivers/scsi/ |
| A D | 53c700.scr | 181 CLEAR ACK
195 CLEAR ACK
199 CLEAR ACK
208 CLEAR ACK
212 CLEAR ACK
216 CLEAR ACK
220 CLEAR ACK
224 CLEAR ACK
232 CLEAR ACK
240 CLEAR ACK
[all …]
|
| A D | 53c700_d.h_shipped | 238 CLEAR ACK
267 CLEAR ACK
280 CLEAR ACK
313 CLEAR ACK
326 CLEAR ACK
339 CLEAR ACK
352 CLEAR ACK
365 CLEAR ACK
382 CLEAR ACK
399 CLEAR ACK
[all …]
|
| /linux/Documentation/translations/zh_CN/process/ |
| A D | stable-kernel-rules.rst | 42 - 如果补丁被接受到队列里，发送者会收到一个ACK回复，如果没有被接受，收
53 - 审查委员会有48小时的时间，用来决定给该补丁回复ACK还是NAK。
57 - 在审查周期结束的时候，那些得到ACK回应的补丁将会被加入到最新的稳定版
|
| /linux/Documentation/translations/zh_TW/process/ |
| A D | stable-kernel-rules.rst | 45 - 如果補丁被接受到隊列裏，發送者會收到一個ACK回覆，如果沒有被接受，收
56 - 審查委員會有48小時的時間，用來決定給該補丁回覆ACK還是NAK。
60 - 在審查週期結束的時候，那些得到ACK回應的補丁將會被加入到最新的穩定版
|
| /linux/Documentation/networking/ |
| A D | snmp_counter.rst | 448 If a packet set ACK flag and has no data, it is a pure ACK packet, if
554 ACK train length.
781 TCP ACK skip
787 counters to indicate the ACK is skipped in which scenario. The ACK
833 The ACK is skipped if the ACK is a challenge ACK. The RFC 5961 defines
863 Delayed ACK
867 `Delayed ACK wiki`_
878 A delayed ACK timer expires, but the TCP stack can't send an ACK
981 Challenge ACK
1106 SYN, sent SYN+ACK, received ACK, so server sent 1 packet, received 2
[all …]
|
| A D | rxrpc.rst | 146 (#) Calls use ACK packets to handle reliability. Data packets are also
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
333 RXRPC_ACK -rt n/a Final ACK received
749 RXRPC_ACK indicates final ACK (no data)
964 RXRPC_SKB_MARK_FINAL_ACK Final ACK received for an incoming call
1113 ACK permits several packets to be ACK'd in one go.
1125 we would send an ACK.
[all …]
|
| A D | plip.rst | 145 D3->ACK 5 - 10 10 - 5
181 INIT -> ACK 16 - 10
211 That raises the ACK line, triggering an interrupt in the receiving
212 machine. The receiving machine disables interrupts and raises its own ACK
|
| /linux/tools/testing/selftests/net/packetdrill/ |
| A D | tcp_md5_md5-only-on-client-ack.pkt | 3 // but then does on the ACK that completes the three-way handshake.
15 // Ooh, weird: client provides MD5 option on the ACK:
22 // Now here comes the legit ACK:
|
| A D | tcp_slow_start_slow-start-ack-per-4pkt.pkt | 4 // In this variant, the receiver sends one ACK per 4 packets.
|
| /linux/Documentation/devicetree/bindings/dma/stm32/ |
| A 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
|
| /linux/tools/testing/selftests/net/netfilter/packetdrill/ |
| A D | conntrack_synack_reuse.pkt | 2 // Challenge ACK is supposed to pass through, RST reply should clear conntrack
8 +0 `iptables -A INPUT -m conntrack --ctstate INVALID -p tcp --tcp-flags SYN,ACK SYN,ACK`
|
| A D | conntrack_inexact_rst.pkt | 9 // 5.772212 client_ip > server_ip TCP 66 45020 > 443 [ACK] Seq=1905874048 Ack=781810658 Win=36352 …
12 // 5.788207 server_ip > client_ip TCP 66 443 > 45020 [FIN, ACK] Seq=781811916 Ack=1905874048 Win=3…
14 // 5.788479 client_ip > server_ip TCP 66 45020 > 443 [RST, ACK] Seq=1905874072 Ack=781811917 Win=3…
|
| A D | conntrack_syn_challenge_ack.pkt | 2 // a challenge-ACK.
24 // Challenge ACK, old incarnation.
|
| A D | conntrack_ack_loss_stall.pkt | 112 …REC=0x00 TTL=255 ID=0 PROTO=TCP SPT=34375 DPT=8080 SEQ=1 ACK=4162510439 WINDOW=257 RES=0x00 ACK PS…
|
| /linux/Documentation/translations/ja_JP/ |
| A D | stable_kernel_rules.txt | 55 - 送信者はパッチがキューに受け付けられた際には ACK を、却下された場合
70 - レビュー委員会は 48時間の間に ACK か NAK を出す。
74 - レビューサイクルの最後に、ACK を受けたパッチは最新の -stable リリー
|
| /linux/tools/testing/selftests/bpf/prog_tests/ |
| A D | cls_redirect.c | 152 ACK, enumerator
201 else if (test->flags == ACK) in test_str()
210 { TCP, ACCEPT, UNKNOWN_CONN, NO_HOPS, ACK },
211 { TCP, FORWARD, UNKNOWN_CONN, ONE_HOP, ACK },
212 { TCP, ACCEPT, KNOWN_CONN, ONE_HOP, ACK },
310 if (test->flags == ACK) in build_input()
|
| /linux/Documentation/input/devices/ |
| A 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
|
| /linux/drivers/gpu/drm/amd/display/dc/link/accessories/ |
| A D | link_dp_cts.c | 534 test_response.bits.ACK = 1; in dp_handle_automated_test()
542 test_response.bits.ACK = 0; in dp_handle_automated_test()
562 test_response.bits.ACK = dm_helpers_dp_handle_test_pattern_request(link->ctx, link, in dp_handle_automated_test()
568 test_response.bits.ACK = 1; in dp_handle_automated_test()
573 test_response.bits.ACK = 1; in dp_handle_automated_test()
577 if (test_response.bits.ACK) in dp_handle_automated_test()
|
| /linux/Documentation/security/ |
| A D | SCTP.rst | 124 Called when a COOKIE ACK is received, and the peer secid will be
128 @skb - pointer to skbuff of the COOKIE ACK packet.
159 <----------------------------------------------- INIT ACK
170 <------------------------------------------- COOKIE ACK
274 Called when a COOKIE ACK is received where it sets the connection's peer sid
278 @skb - pointer to skbuff of the COOKIE ACK packet.
|
| /linux/Documentation/driver-api/surface_aggregator/ |
| A 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
|
| /linux/Documentation/i2c/ |
| A D | slave-interface.rst | 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
|
| 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.
|
| /linux/drivers/usb/gadget/udc/ |
| A D | goku_udc.c | 1529 #define ACK(irqbit) { \ macro
1580 ACK(INT_SUSPEND); in goku_irq()
1617 ACK(INT_USBRESET); in goku_irq()
1628 ACK(INT_SETUP); in goku_irq()
1633 ACK(INT_STATUSNAK|INT_ENDPOINT0); in goku_irq()
1643 ACK(INT_ENDPOINT0); in goku_irq()
1651 ACK(INT_MSTRDEND); in goku_irq()
1657 ACK(INT_MSTWREND); in goku_irq()
1663 ACK(INT_MSTWRTMOUT); in goku_irq()
1697 #undef ACK
|
| /linux/Documentation/core-api/ |
| A D | netlink.rst | 35 not via the ACK. Try to find useful data to return. Once the command is
36 added whether it replies with a full message or only an ACK is uAPI and
|
| /linux/include/rdma/ |
| A D | tid_rdma_defs.h | 94 IB_OPCODE(TID_RDMA, ACK),
|