> -Original Message-
> From: Zhang, Qi Z
> Sent: Wednesday, June 28, 2023 4:59 PM
> To: Lu, Wenzhuo ; dev@dpdk.org
> Cc: sta...@dpdk.org
> Subject: RE: [PATCH] net/iavf: fix VLAN insertion in vector path
>
>
>
> > -Original Message-
> >
> -Original Message-
> From: Lu, Wenzhuo
> Sent: Wednesday, June 28, 2023 3:13 PM
> To: Zhang, Qi Z ; dev@dpdk.org
> Cc: sta...@dpdk.org
> Subject: RE: [PATCH] net/iavf: fix VLAN insertion in vector path
>
> Hi Qi,
>
> > -Original Message
Hi Qi,
> -Original Message-
> From: Zhang, Qi Z
> Sent: Wednesday, June 28, 2023 2:57 PM
> To: Lu, Wenzhuo ; dev@dpdk.org
> Cc: Lu, Wenzhuo ; sta...@dpdk.org
> Subject: RE: [PATCH] net/iavf: fix VLAN insertion in vector path
>
> We may need to update the iavf.i
> -Original Message-
> From: Wenzhuo Lu
> Sent: Wednesday, June 21, 2023 9:19 AM
> To: dev@dpdk.org
> Cc: Lu, Wenzhuo ; sta...@dpdk.org
> Subject: [PATCH] net/iavf: fix VLAN insertion in vector path
>
> As the VLAN insertion is partially supported in vect
As the VLAN insertion is partially supported in vector path,
the behavior is different in scalar and vector path.
For a VLAN packet, if using scalar path, the new VLAN tag will
be inserted after the original VLAN tag. If using vector path,
the new VLAN tag is inserted before the original VLAN tag.
5 matches
Mail list logo