Lines Matching refs:checksum

8  to take advantage of checksum offload capabilities of various NICs.
23 The interface for offloading a transmit checksum to a device is explained
26  checksum defined by the sk_buff fields skb->csum_start and
28  checksum (i.e. the 'IP-style' checksum) from csum_start to the end of the
31  value of the checksum field is included in the checksum computation, thus
32  it can be used to supply any needed corrections to the checksum (such as
34 This interface only allows a single checksum to be offloaded.  Where
35  encapsulation is used, the packet may have multiple checksum fields in
38 No offloading of the IP header checksum is performed; it is always done in
56 The stack should, for the most part, assume that checksum offload is
69 LCO is a technique for efficiently computing the outer checksum of an
70  encapsulated datagram when the inner checksum is due to be offloaded.
73  else gets 'cancelled out' by the checksum field.  This is because the sum was
74  complemented before being written to the checksum field.
76  checksum is used, and thus any checksum that TX Checksum Offload supports.
78  know that after the device has filled in that checksum, the ones
80  the complement of whatever value we put in the checksum field beforehand.
81  This allows us to compute the outer checksum without looking at the payload:
84 Then, when the true inner checksum is filled in (either by hardware or by
85  skb_checksum_help()), the outer checksum will become correct by virtue of
93  constructing an IPv6 GRE header; the GRE checksum is computed over the
95  possible to use LCO here as IPv6 GRE still uses an IP-style checksum.
109 RCO is a technique for eliding the inner checksum of an encapsulated
110  datagram, allowing the outer checksum to be offloaded.  It does, however,