Searched refs:acknowledgment (Results 1 – 21 of 21) sorted by relevance
/linux/Documentation/devicetree/bindings/net/ |
H A D | qcom,bam-dmux.yaml | 33 - description: Power control acknowledgment 45 - description: Power control acknowledgment
|
/linux/LICENSES/deprecated/ |
H A D | Zlib | 23 product, an acknowledgment in the product documentation would be appreciated
|
/linux/drivers/net/ethernet/ti/icssg/ |
H A D | icssg_config.h | 171 u8 acknowledgment; member
|
H A D | icssg_prueth.c | 354 if (readb(&sc_descp->acknowledgment)) in prueth_iep_settime()
|
/linux/block/ |
H A D | opal_proto.h | 254 __be32 acknowledgment; member
|
/linux/Documentation/driver-api/surface_aggregator/ |
H A D | internal.rst | 67 acknowledgment (ACKing), packet (retransmission) timeouts, and relaying 170 been transmitted, but wait for acknowledgment (e.g. the corresponding ACK 174 re-submitted due to a packet acknowledgment timeout or NAK. On such a 222 The packet acknowledgment timeout is a per-packet timeout for sequenced 242 Note that due to transmission and packet acknowledgment timeouts, the packet 425 This timeout is, similar to the packet acknowledgment timeout on the packet 434 acknowledgment timeouts, guarantees that the request layer will always make
|
/linux/Documentation/virt/kvm/x86/ |
H A D | cpuid.rst | 92 async pf acknowledgment msr
|
H A D | msr.rst | 371 Asynchronous page fault (APF) acknowledgment.
|
/linux/Documentation/devicetree/bindings/mailbox/ |
H A D | fsl,mu.yaml | 83 acknowledgment support.
|
/linux/Documentation/virt/kvm/devices/ |
H A D | xive.rst | 29 handle priority management and interrupt acknowledgment. The most
|
/linux/Documentation/mhi/ |
H A D | mhi.rst | 19 protocol provides data acknowledgment feature and manages the power state of the
|
/linux/scripts/ |
H A D | spelling.txt | 55 acknowldegement||acknowledgment 56 acknowledgement||acknowledgment
|
/linux/Documentation/admin-guide/device-mapper/ |
H A D | vdo.rst | 394 Bio acknowledgment threads are used for finishing I/O requests. This is
|
H A D | vdo-design.rst | 421 acknowledged at this point. The acknowledgment happens on a separate 595 acknowledgment as in step 13, although it only needs to release the logical
|
/linux/drivers/scsi/lpfc/ |
H A D | lpfc_hw.h | 2288 uint32_t acknowledgment:1; member 2302 uint32_t acknowledgment:1;
|
/linux/Documentation/networking/ |
H A D | rds.rst | 196 piggybacked acknowledgment of last packet received
|
H A D | ip-sysctl.rst | 226 acknowledgment, which means the route was installed in the kernel, 479 (b) out-of-window acknowledgment number, or 536 which have not received an acknowledgment from connecting client. 2153 acknowledgment, which means the route was installed in the kernel, 3186 acknowledgment to a probe packet. This is also the time interval
|
H A D | timestamping.rst | 140 cumulative acknowledgment. The mechanism ignores SACK and FACK.
|
H A D | rxrpc.rst | 149 (#) There are two types of positive acknowledgment: hard-ACKs and soft-ACKs.
|
/linux/Documentation/filesystems/ |
H A D | autofs.rst | 415 and no acknowledgment is needed.
|
/linux/Documentation/admin-guide/ |
H A D | reporting-issues.rst | 1437 then should at least have sent some kind of acknowledgment.
|