> -Original Message-
> From: Zhou, YidingX
> Sent: Thursday, November 10, 2022 10:10 AM
> To: Zhang, Qi Z ; dev@dpdk.org
> Cc: ktray...@redhat.com; Yang, Qiming
> Subject: RE: [PATCH v3] net/iavf: revert fix VLAN insertion
>
> > > Subject: [PATCH
> > Subject: [PATCH v3] net/iavf: revert fix VLAN insertion
> >
> > The vector Tx path does not support VLAN insertion via the L2TAG2
> > field, but the scalar path supports. The previous commit was to force
> > to select scalar path as soon as kernel driver request
> -Original Message-
> From: Yiding Zhou
> Sent: Friday, November 4, 2022 2:10 PM
> To: dev@dpdk.org
> Cc: ktray...@redhat.com; Yang, Qiming ; Zhou,
> YidingX
> Subject: [PATCH v3] net/iavf: revert fix VLAN insertion
>
> The vector Tx path does not sup
Hi
> -Original Message-
> From: Zhou, YidingX
> Sent: Friday, November 4, 2022 2:10 PM
> To: dev@dpdk.org
> Cc: ktray...@redhat.com; Yang, Qiming ; Zhou,
> YidingX
> Subject: [PATCH v3] net/iavf: revert fix VLAN insertion
>
> The vector Tx path does not sup
The vector Tx path does not support VLAN insertion via the L2TAG2 field,
but the scalar path supports. The previous commit was to force to select
scalar path as soon as kernel driver requests to use L2TAG2.
That logic is incorrect. Because other case like VLAN offloading not
required but scalar pa
5 matches
Mail list logo
