Data Sheet

Ethernet Controller I210 —Packet Types
868
A.1.5.2.4 Type 3.2.1: NFS Read Response (NFSv4)
In this case the NFS header size is (36+D+F) bytes. This length should be added to the UDP/TCP type
that was already parsed.
A.2 IP and TCP/UDP Headers for TSO
This section outlines the format and content for the IP, TCP and UDP headers. The I210 requires
baseline information from the software device driver in order to construct the appropriate header
information during the segmentation process.
Header fields that are modified by the I210 are highlighted in the figures that follow.
Note: IPv4 requires the use of a checksum for the header. IPv6 does not use a header checksum.
IPv4 length includes the TCP and IP headers, and data. IPv6 length does not include the IPv6 header.
Note: The IP header is first shown in the traditional (such as RFC 791) representation, and because
byte and bit ordering is confusing in that representation, the IP header is also shown in little
endian format. The actual data is fetched from memory in little endian format.
Offset # of Bytes Field Value (hex) Action Comment
RPC Header
0 D =(0/4) Record Header - Ignore
If the previous header was
TCP header than this field
contain 4 bytes
0+D 4XID - Ignore
4+D 4 Message type 0x01 Compare
8+D 4 Reply status 0x00 Ignore
‘0’ means O.K and only if
this value is ‘0’ there will be
additional data
12+D 4 Verifier Flavor - Ignore
16+D 4 Verifier Size (VSZ) <400 Check
20+D F Verifier Data - Ignore F = (VSZ pad 4)
20+D+F 4 Accept status 0x00 Ignore ‘0’ means O.K
NFS Header
24+D+F 4 Status 0x00 Ignore ‘0’ means O.K
28+D+F 4eof - Ignore
32+D+F 4 Data len - Ignore
Table A-1. IPv4 Header (Traditional Representation)
1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
Version IP Hdr Length TYPE of service
Total length
Identification Flags Fragment Offset
Time to Live Layer 4 Protocol ID
Header Checksum