> -----Original Message-----
> From: Lu, Wenzhuo <[email protected]>
> Sent: Wednesday, March 29, 2023 9:06 AM
> To: mschmidt <[email protected]>; [email protected]
> Cc: Richardson, Bruce <[email protected]>; Konstantin Ananyev
> <[email protected]>; Wu, Jingjing <[email protected]>;
> Xing, Beilei <[email protected]>; Rong, Leyi <[email protected]>;
> [email protected]
> Subject: RE: [PATCH] net/iavf: fix VLAN offload with AVX512
>
>
>
> > -----Original Message-----
> > From: Michal Schmidt <[email protected]>
> > Sent: Monday, March 27, 2023 6:08 PM
> > To: [email protected]
> > Cc: Richardson, Bruce <[email protected]>; Konstantin Ananyev
> > <[email protected]>; Wu, Jingjing
> > <[email protected]>; Xing, Beilei <[email protected]>; Rong,
> > Leyi <[email protected]>; Lu, Wenzhuo <[email protected]>;
> > [email protected]
> > Subject: [PATCH] net/iavf: fix VLAN offload with AVX512
> >
> > 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.
> >
> > This fix is for the AVX512 Rx path. The same bug in AVX2 was fixed by
> > commit
> > eb24917428a1 ("net/iavf: fix VLAN offload with AVX2").
> >
> > Fixes: 4b64ccb328c9 ("net/iavf: fix VLAN extraction in AVX512 path")
> > Cc: [email protected]
> >
> > Signed-off-by: Michal Schmidt <[email protected]>
> Acked-by: Wenzhuo Lu <[email protected]>
Applied to dpdk-next-net-intel.
Thanks
Qi
