> -----Original Message----- > From: Lu, Wenzhuo <[email protected]> > Sent: Wednesday, December 14, 2022 10:06 AM > To: mschmidt <[email protected]>; [email protected] > Cc: Richardson, Bruce <[email protected]>; Wu, Jingjing > <[email protected]>; Xing, Beilei <[email protected]>; Wang, Haiyue > <[email protected]> > Subject: RE: [PATCH] net/iavf: fix mbuf VLAN offload flags in the L2TAG2 > path with AVX2 > > > > > -----Original Message----- > > From: Michal Schmidt <[email protected]> > > Sent: Thursday, December 8, 2022 8:19 PM > > To: [email protected] > > Cc: Richardson, Bruce <[email protected]>; Wu, Jingjing > > <[email protected]>; Xing, Beilei <[email protected]>; Wang, > > Haiyue <[email protected]> > > Subject: [PATCH] net/iavf: fix mbuf VLAN offload flags in the L2TAG2 > > path with > > AVX2 > > > > It has been observed that mbufs of some received VLAN packets had the > > VLAN tag correctly set in vlan_tci, but ol_flags were missing the > > VLAN-indicating flags. > > > > _mm256_shuffle_epi8 operates as two independent 128-bit operations, > > not as a single 256-bit operation. To have the RTE_MBUF_F_RX_VLAN* > > flags reflected in the resulting vlan_flags for all 8 rx descriptors, > > the input l2tag2_flags_shuf must contain the required pattern in both 128- > bit halves. > > > > Fixes: 3a1aca384d3a ("net/iavf: fix VLAN tag extraction handling") > > > > Signed-off-by: Michal Schmidt <[email protected]> > Acked-by: Wenzhuo Lu <[email protected]> Applied to dpdk-next-net-intel. Thanks Qi
