Page MenuHomeFreeBSD

sfxge(4): add information if TSO workaround is required
ClosedPublic

Authored by arybchik on Nov 21 2018, 11:54 AM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Dec 17, 10:51 AM
Unknown Object (File)
Tue, Dec 10, 7:10 AM
Unknown Object (File)
Sat, Nov 30, 3:27 PM
Unknown Object (File)
Sat, Nov 30, 1:58 PM
Unknown Object (File)
Nov 1 2024, 2:49 PM
Unknown Object (File)
Oct 21 2024, 6:31 PM
Unknown Object (File)
Oct 21 2024, 6:31 PM
Unknown Object (File)
Oct 21 2024, 6:31 PM
Subscribers

Details

Summary

In SF bug 61297 it's been confirmed that the hardware does not always
calculate the TCP checksum correctly with TSO sends.

The value of the Total Length field (IPv4) or Payload Length field
(IPv6) is the critical factor. We're sufficiently confident that if
these fields are zero then the checksum will be calculated correctly.

The information may be used by the drivers to check if the workaround is
required when FATSOv2 is implemented.

Submitted by: Mark Spender <mspender at solarflare.com>
Sponsored by: Solarflare Communications, Inc.

Test Plan

amd64 tinderbox kernel builds tested
driver loaded/unloaded, interfaces up/down, traffic works fine

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

This revision was not accepted when it landed; it landed in state Needs Review.Nov 30 2018, 7:07 AM
This revision was automatically updated to reflect the committed changes.