Searched full:sender (Results 1 – 25 of 25) sorted by relevance
| /Documentation/driver-api/md/ |
| D | md-cluster.rst | 75 Messages can be broadcast to all nodes, and the sender waits for all
153 sender receiver receiver
156 2. sender get EX on "token",
157 sender get EX on "message"::
159 sender receiver receiver
164 Sender checks that it still needs to send a message. Messages
168 3. sender writes LVB
170 sender down-convert "message" from EX to CW
172 sender try to get EX of "ack"
186 sender receiver receiver
[all …]
|
| /Documentation/infiniband/ |
| D | tag_matching.rst | 21 When a message is sent from the sender to the receiver, the communication
32 processed by the sender. A completion send is received in the send_cq
35 2. The Rendezvous Protocol - the sender sends the tag-matching header,
|
| /Documentation/networking/ |
| D | dccp.txt | 110 accepted by the receiver. Hence, when using this feature on the sender, it must
113 DCCP_SOCKOPT_SEND_CSCOV sets the sender checksum coverage. Values in the
161 Default CCID for the sender-receiver half-connection. Depending on the
165 Default CCID for the receiver-sender half-connection; see tx_ccid.
168 The initial sequence window (sec. 7.5.2) of the sender. This influences
|
| D | netconsole.txt | 22 Sender and receiver configuration:
184 the sender, it is suggested to try specifying the MAC address of the
194 printing all messages from the sender, it is likely that you have set
195 the "console_loglevel" parameter (on the sender) to only send high
|
| D | udplite.txt | 57 * Sender checksum coverage: UDPLITE_SEND_CSCOV
114 1) Sender Socket Options
116 If the sender specifies a value of 0 as coverage length, the module
118 and according checksum. If the sender specifies a coverage < 8 and
138 On both sender and receiver, checksumming will always be performed
|
| D | ipsec.txt | 5 1. IPcomp: Small IP packet won't get compressed at sender, and failed on
|
| D | snmp_counter.rst | 597 packet, so the sender needs to retransmit this packet. In this
598 situation, the sender adds 1 to TcpExtTCPSACKReneging. A receiver
600 unusual, it is allowed by the TCP protocol. The sender doesn't really
601 know what happened on the receiver side. The sender just waits until
602 the RTO expires for this packet, then the sender assumes this packet
613 order packet. Thus the sender would find more ACks than its
614 expectation, and the sender knows out of order occurs.
619 sender sends packet 1,2,3,4,5, and the receiving order is
620 1,2,4,5,3. When the sender receives the ACK of packet 3 (which will
629 detect reorder: (1) DSACK is received by the sender. It means the
[all …]
|
| D | rds.txt | 220 Sending an ack immediately would allow the sender to free the sent
224 in flight at a time, and by the sender only asking for acks when
257 communication of per-port congestion. The sender does a very
413 number of paths supported by the sender. The "probe" ping packet will
421 ignored. In this case the pong will not have any exthdrs, so the sender
|
| D | phonet.txt | 29 uint8_t pn_sdev; /* Sender device ID */
33 uint8_t pn_sobj; /* Sender object ID */
|
| D | xfrm_sync.txt | 136 A response is issued back to the sender in user space to indicate success
|
| D | ip-sysctl.txt | 334 RTT fluctuates (e.g., wireless). F-RTO is sender-side only
799 TCP bulk sender tends to increase packets in flight until it
1307 the level announces more valid sender's information.
1318 sender's IP address are part from same subnet on this interface
1879 omitted since the sender of the solicitation has the correct link-
1883 race condition where the sender deletes the cached link-layer address
|
| D | rxrpc.txt | 152 been received but may yet be discarded and re-requested. The sender may
1099 generate a soft-ACK to tell the sender that it doesn't need to resend.
1105 the sender it can free its buffers, assuming no other reason occurs that
|
| D | timestamping.txt | 501 * the sender of the packet decides which are to be
|
| D | arcnet-hardware.txt | 48 tell the sender about it.
|
| /Documentation/devicetree/bindings/mailbox/ |
| D | amlogic,meson-gxbb-mhu.yaml | 18 data has been read by the remote. This driver assumes the sender polls
|
| D | arm-mhu.txt | 8 data has been read by the remote. This driver assumes the sender polls
|
| /Documentation/hid/ |
| D | intel-ish-hid.rst | 196 the sender that the memory region for that message may be reused.
209 At initial state all outgoing memory belongs to the sender (TX to host, RX to
211 the receiving side, DMA_XFER_ACK returns ownership to the sender. A sender
|
| /Documentation/translations/zh_CN/process/ |
| D | email-clients.rst | 175 # Sender, email address, and sign-off line must match
|
| /Documentation/process/ |
| D | stable-kernel-rules.rst | 142 - The sender will receive an ACK when the patch has been accepted into the
|
| D | email-clients.rst | 232 # Sender, email address, and sign-off line must match
|
| D | howto.rst | 408 mail twice, one from the sender and the one from the list, and don't try
|
| /Documentation/virt/kvm/ |
| D | vcpu-requests.rst | 87 The VCPU thread is outside guest mode, but it wants the sender of
|
| /Documentation/networking/device_drivers/chelsio/ |
| D | cxgb.txt | 158 Bandwidth-Delay Product of the communication link between the sender and
|
| /Documentation/admin-guide/LSM/ |
| D | Smack.rst | 588 one process to another requires that the sender have write access to the
589 receiver. The receiver is not required to have read access to the sender.
|
| /Documentation/admin-guide/ |
| D | devices.txt | 2526 184 char Picture Elements' video simulator/sender
2527 0 = /dev/pevss0 First sender board
2528 1 = /dev/pevss1 Second sender board
|