summaryrefslogtreecommitdiff
path: root/crypto
diff options
context:
space:
mode:
authorSalil <salil.mehta@huawei.com>2016-12-06 14:09:46 +0300
committerDavid S. Miller <davem@davemloft.net>2016-12-06 19:41:57 +0300
commit862b3d2090ae3d8b10bb4ee9275fd932bc4d0d44 (patch)
tree535aad3a3a4ad981c4fd419702cd3020aeb7387b /crypto
parent48e0a83ece7803a62afd624ba70523ca66631c35 (diff)
downloadlinux-862b3d2090ae3d8b10bb4ee9275fd932bc4d0d44.tar.xz
net: hns: Fix to conditionally convey RX checksum flag to stack
This patch introduces the RX checksum function to check the status of the hardware calculated checksum and its error and appropriately convey status to the upper stack in skb->ip_summed field. In hardware, we only support checksum for the following protocols: 1) IPv4, 2) TCP(over IPv4 or IPv6), 3) UDP(over IPv4 or IPv6), 4) SCTP(over IPv4 or IPv6) but we support many L3(IPv4, IPv6, MPLS, PPPoE etc) and L4(TCP, UDP, GRE, SCTP, IGMP, ICMP etc.) protocols. Hardware limitation: Our present hardware RX Descriptor lacks L3/L4 checksum "Status & Error" bit (which usually can be used to indicate whether checksum was calculated by the hardware and if there was any error encountered during checksum calculation). Software workaround: We do get info within the RX descriptor about the kind of L3/L4 protocol coming in the packet and the error status. These errors might not just be checksum errors but could be related to version, length of IPv4, UDP, TCP etc. Because there is no-way of knowing if it is a L3/L4 error due to bad checksum or any other L3/L4 error, we will not (cannot) convey hardware checksum status(CHECKSUM_UNNECESSARY) for such cases to upper stack and will not maintain the RX L3/L4 checksum counters as well. Signed-off-by: Salil Mehta <salil.mehta@huawei.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions