Lines Matching refs:checksum

12 take advantage of checksum offload capabilities of various NICs.
29 The interface for offloading a transmit checksum to a device is explained in
33 checksum defined by the sk_buff fields skb->csum_start and skb->csum_offset.
34 The device should compute the 16-bit ones-complement checksum (i.e. the
35 'IP-style' checksum) from csum_start to the end of the packet, and fill in the
39 the checksum field is included in the checksum computation, thus it can be used
40 to supply any needed corrections to the checksum (such as the sum of the
43 This interface only allows a single checksum to be offloaded.  Where
44 encapsulation is used, the packet may have multiple checksum fields in
52 No offloading of the IP header checksum is performed; it is always done in
71 The stack should, for the most part, assume that checksum offload is supported
84 LCO is a technique for efficiently computing the outer checksum of an
85 encapsulated datagram when the inner checksum is due to be offloaded.
89 'cancelled out' by the checksum field.  This is because the sum was
90 complemented before being written to the checksum field.
93 checksum is used, and thus any checksum that TX Checksum Offload supports.
96 know that after the device has filled in that checksum, the ones complement sum
98 whatever value we put in the checksum field beforehand.  This allows us to
99 compute the outer checksum without looking at the payload: we simply stop
103 Then, when the true inner checksum is filled in (either by hardware or by
104 skb_checksum_help()), the outer checksum will become correct by virtue of the
113 constructing an IPv6 GRE header; the GRE checksum is computed over the whole
115 LCO here as IPv6 GRE still uses an IP-style checksum.
130 RCO is a technique for eliding the inner checksum of an encapsulated datagram,
131 allowing the outer checksum to be offloaded.  It does, however, involve a