Lines Matching refs:coverage
33 IPPROTO need to be changed; senders additionally set the checksum coverage
52 using partial checksum coverage and so emulate UDP mode (full coverage).
54 To make use of the partial checksum coverage facilities requires setting a
55 single socket option, which takes an integer specifying the coverage length:
57 * Sender checksum coverage: UDPLITE_SEND_CSCOV
64 sets the checksum coverage length to 20 bytes (12b data + 8b header).
70 * Receiver checksum coverage: UDPLITE_RECV_CSCOV
73 required to enable traffic with partial checksum coverage. Its function is
75 all packets which have a coverage _less_ than this value. For example, if
77 packets with a minimum coverage of 20 are admitted:
86 A detailed discussion of UDP-Lite checksum coverage options is in section IV.
116 If the sender specifies a value of 0 as coverage length, the module
117 assumes full coverage, transmits a packet with coverage length of 0
118 and according checksum. If the sender specifies a coverage < 8 and
120 if the specified coverage length exceeds the packet length, the packet
121 length is used instead as coverage length.
125 The receiver specifies the minimum value of the coverage length it
133 All packets arriving with a coverage value less than the specified
169 The send buffer size has implications on the checksum coverage length.
180 The coverage packet covers the UDP-Lite header and 848 bytes of the
182 that for the second packet, the coverage length exceeds the packet
183 length. The kernel always re-adjusts the coverage length to the packet
197 *****checksum coverage*************
207 coverage is less than 1232 bytes (MTU minus IPv6/fragment header
209 larger checksum coverage lengths, each eligible fragment needs to be
210 checksummed. Suppose we have a checksum coverage of 3062. The buffer
223 coverage lengths are likely to be expected.
244 coverage length exceeds received length)
246 * application has specified larger min. coverage
248 * checksum coverage violated