Searched refs:checksum (Results 1 – 25 of 44) sorted by relevance
12
| /Documentation/networking/ |
| D | checksum-offloads.txt | 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
[all …]
|
| D | udplite.txt | 7 is a variable-length checksum. This has advantages for transport of multimedia
9 fed into the codec instead of being discarded due to a failed checksum test.
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
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
86 A detailed discussion of UDP-Lite checksum coverage options is in section IV.
[all …]
|
| D | segmentation-offloads.txt | 26 TCP segmentation is dependent on support for the use of partial checksum
27 offload. For this reason TSO is normally disabled if the Tx checksum
83 fact that the outer header also requests to have a non-zero checksum
87 has requested a remote checksum offload. In this case the inner headers
88 will be left with a partial checksum and only the outer header checksum
123 offloads or tunnel offloads with checksum to still make use of segmentation.
|
| D | tcp.txt | 96 checksum in the copy.
104 and recompute. We add any new tcp level headers and refinish the checksum
|
| D | s2io.txt | 16 such as jumbo frames, MSI/MSI-X, checksum offloads, TSO, UFO and so on.
43 b. Offloads. Supports checksum offload(TCP/UDP/IP) on transmit
|
| D | dccp.txt | 108 partial checksum coverage (RFC 4340, sec. 9.2). The default is that checksums
113 DCCP_SOCKOPT_SEND_CSCOV sets the sender checksum coverage. Values in the
206 because the checksum covers the pseudo-header as per TCP and UDP. Linux NAT
|
| D | ena.txt | 27 as checksum offload and TCP transmit segmentation offload (TSO).
236 - IPv4 header checksum offload
237 - TCP/UDP over IPv4/IPv6 checksum offloads
304 checksum hw verify result, etc.), and then passed to the network
|
| D | nf_conntrack-sysctl.txt | 22 Verify checksum of incoming packets. Packets with bad checksums are
|
| D | 00-INDEX | 45 checksum-offloads.txt
46 - Explanation of checksum offloads; LCO, RCO
|
| D | 6pack.txt | 30 - Each packet transferred over the serial line is supplied with a checksum,
145 bad checksum', which is due to data loss if the other station sends two
|
| D | dm9000.txt | 160 2) TCP/UDP checksum offloading, which the driver does not currently support.
|
| D | netdev-features.txt | 108 It means that device can fill TCP/UDP-like checksum anywhere in the packets
|
| /Documentation/input/ |
| D | walkera0701.txt | 90 absolute binary value. (10 bits per channel). Next nibble is checksum for
96 checksum for nibbles 12..23.
105 Summary of octal values in nibbles must be same as octal value in checksum
106 nibble (only first 3 bits are used). Binary value for checksum nibble is
|
| /Documentation/devicetree/bindings/net/ |
| D | marvell-orion-net.txt | 30 - marvell,tx-checksum-limit: max tx packet size for hardware checksum.
74 marvell,tx-checksum-limit = <1600>;
|
| D | marvell-armada-370-neta.txt | 14 - tx-csum-limit: maximum mtu supported by port that allow TX checksum.
|
| /Documentation/block/ |
| D | data-integrity.txt | 16 checksum for each sector as well as an incrementing counter that
56 Also, the 16-bit CRC checksum mandated by both the SCSI and SATA specs
58 calculating this checksum had a significant impact on system
60 lighter-weight checksum to be used when interfacing with the operating
61 system. Emulex, for instance, supports the TCP/IP checksum instead.
62 The IP checksum received from the OS is converted to the 16-bit CRC
67 The IP checksum is weaker than the CRC in terms of detecting bit
|
| /Documentation/nfc/ |
| D | nfc-pn544.txt | 27 checksum. Firmware update messages have the length in the second (MSB)
|
| /Documentation/ia64/ |
| D | README | 37 include the library routines (IP checksum, etc.). Less
|
| /Documentation/filesystems/ |
| D | romfs.txt | 65 12 | checksum | The checksum of the FIRST 512 BYTES.
79 is the checksum of the first 512 bytes (or the number of bytes
98 12 | checksum | Covering the meta data, including the file
|
| /Documentation/infiniband/ |
| D | ipoib.txt | 56 TCP/IP checksum and/or Large Send (LSO) offloading capability to the
61 checksum offload capable devices.
|
| /Documentation/EDID/ |
| D | edid.S | 272 checksum: .byte CRC /* Sum of all bytes must be 0 */ label
|
| /Documentation/hwmon/ |
| D | sht21 | 48 Different resolutions, the on-chip heater, using the CRC checksum and reading
|
| D | sht15 | 57 * checksum:
|
| /Documentation/scsi/ |
| D | arcmsr_spec.txt | 113 ** command code, data and checksum byte
125 ** (E) last byte : checksum byte (sum of 1st byte until last data byte)
554 ** (low byte 1st, excludes length and checksum byte)
573 ** (E) Checksum : checksum of length and status or data byte
|
| /Documentation/networking/caif/ |
| D | Linux-CAIF.txt | 110 and frame checksum.
|
12