diff options
author | Subash Abhinov Kasiviswanathan <subashab@codeaurora.org> | 2018-01-07 11:36:36 -0700 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2018-01-08 13:58:49 -0500 |
commit | c597897b08cb56e6a8b240245c074d43d1fde735 (patch) | |
tree | 28c0be519ac9109d31cd256ddc0c10645c5feadd /drivers/net/ethernet/qualcomm/rmnet/rmnet_map_data.c | |
parent | 4e8683a95c963d766c7341eddbbc2d0c20022ebf (diff) | |
download | linux-stable-c597897b08cb56e6a8b240245c074d43d1fde735.tar.gz |
net: qualcomm: rmnet: Define the MAPv4 packet formats
The MAPv4 packet format adds support for RX / TX checksum offload.
For a bi-directional UDP stream at a rate of 570 / 146 Mbps, roughly
10% CPU cycles are saved.
For receive path, there is a checksum trailer appended to the end of
the MAP packet. The valid field indicates if hardware has computed
the checksum. csum_start_offset indicates the offset from the start
of the IP header from which hardware has computed checksum.
csum_length is the number of bytes over which the checksum was
computed and the resulting value is csum_value.
In the transmit path, a header is appended between the end of the MAP
header and the start of the IP packet. csum_start_offset is the offset
in bytes from which hardware will compute the checksum if the
csum_enabled bit is set. udp_ip4_ind indicates if the checksum
value of 0 is valid or not. csum_insert_offset is the offset from the
csum_start_offset where hardware will insert the computed checksum.
The use of this additional packet format for checksum offload is
explained in subsequent patches.
Signed-off-by: Subash Abhinov Kasiviswanathan <subashab@codeaurora.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/ethernet/qualcomm/rmnet/rmnet_map_data.c')
0 files changed, 0 insertions, 0 deletions