On 4/20/2018 11:02 PM, Yong Wang wrote: >> -----Original Message----- >> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Didier Pallard >> Sent: Wednesday, March 28, 2018 8:44 AM >> To: dev@dpdk.org >> Subject: [dpdk-dev] [PATCH 0/8] net/vmxnet3: fix offload issues >> >> This patchset fixes several issues found in vmxnet3 driver >> when enabling LRO offload support: >> - Rx offload information are not correctly gathered in >> multisegmented packets, leading to inconsistent >> packet type and Rx offload bits in resulting mbuf >> - MSS recovery from offload information is not done >> thus LRO mbufs do not contain a correct tso_segsz value. >> - MSS value is not propagated by the host on some >> hypervisor versions (6.0 for example) >> - If two small TCP segments are aggregated in a single >> mbuf, an empty segment that only contains offload >> information is appended to this segment, and is >> propagated as is to the application. But if the application >> sends back to the hypervisor a mbuf with an empty >> segment, this mbuf is dropped by the hypervisor. >> >> >> Didier Pallard (8): >> net: export IPv6 header extensions skip function >> net/vmxnet3: return unknown IPv4 extension len ptype >> net/vmxnet3: gather offload data on first and last segment >> net/vmxnet3: fix Rx offload information in multiseg packets >> net/vmxnet3: complete Rx offloads support >> net/vmxnet3: guess mss if not provided in LRO mode >> net/vmxnet3: ignore emtpy segments in reception >> net/vmxnet3: skip empty segments in transmission
<...> > For this series, > Acked-by: Yong Wang <yongw...@vmware.com> Series applied to dpdk-next-net/master, thanks.
