> -----Original Message-----
> From: Thomas Monjalon <[email protected]>
> Sent: Tuesday, June 13, 2023 2:02 AM
> To: Zhang, Qi Z <[email protected]>
> Cc: Lu, Wenzhuo <[email protected]>; mschmidt
> <[email protected]>; [email protected]; Richardson, Bruce
> <[email protected]>; Konstantin Ananyev
> <[email protected]>; Wu, Jingjing <[email protected]>;
> Xing, Beilei <[email protected]>; Rong, Leyi <[email protected]>;
> [email protected]; Zhang, Helin <[email protected]>;
> [email protected]
> Subject: Re: [PATCH] net/iavf: fix VLAN offload with AVX512
>
> 03/04/2023 07:39, Zhang, Qi Z:
> > > > 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.
>
> I don't find this patch in your tree.
> Is it lost somewhere?
Sorry, it is merged now.
>
>
