Thread (9 messages) read the whole thread 9 messages, 4 authors, 2021-02-02

Re: [dpdk-dev] ixgbe and UDP with zero checksum

From: Aaron Conole <aconole@redhat.com>
Date: 2021-01-27 18:21:17

"Wang, Haiyue" [off-list ref] writes:
Hi Paolo,
quoted
-----Original Message-----
From: Paolo Valerio <redacted>
Sent: Wednesday, January 27, 2021 21:50
To: dev@dpdk.org
Cc: Guo, Jia <redacted>; Wang, Haiyue <redacted>; Aaron Conole
[off-list ref]
Subject: ixgbe and UDP with zero checksum

Hi,

performing some tests, I noticed that on ixgbe when receiving UDP
packets with zero checksum (no checksum) over IPv4, the corresponding
ol_flag for the l4 checksum is set to PKT_RX_L4_CKSUM_BAD.

In particular, this apparently has an impact on OvS using ct() action
where UDP packets with zero checksum are not tracked because of that.
quoted
[1]
https://patchwork.ozlabs.org/project/netdev/patch/20090724040031.30202.1531.stgit@localhost.localdomai
n/
About 12 years old patch, it is hardware errata. For fixing this,
have to always disable vector Rx path for 82599, it seems not a
good idea to bring in this workaround. :(
Just wondering that it means here - there's a user of DPDK who has an
ixgbe card exhibiting this behavior.  What do DPDK engineers tell them
to do?  Change the hardware?  Upgrade the firmware?
+		/*
+		 * 82599 errata, UDP frames with a 0 checksum can be marked as
+		 * checksum errors.
+		 */
+		if ((pkt_info & IXGBE_RXDADV_PKTTYPE_UDP) &&
+		    (adapter->hw.mac.type == ixgbe_mac_82599EB))
+			return;
quoted
Regards,
Paolo
  
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help