> -----Original Message-----
> From: Lu, Wenzhuo <[email protected]>
> Sent: Wednesday, June 28, 2023 3:13 PM
> To: Zhang, Qi Z <[email protected]>; [email protected]
> Cc: [email protected]
> Subject: RE: [PATCH] net/iavf: fix VLAN insertion in vector path
>
> Hi Qi,
>
> > -----Original Message-----
> > From: Zhang, Qi Z <[email protected]>
> > Sent: Wednesday, June 28, 2023 2:57 PM
> > To: Lu, Wenzhuo <[email protected]>; [email protected]
> > Cc: Lu, Wenzhuo <[email protected]>; [email protected]
> > Subject: RE: [PATCH] net/iavf: fix VLAN insertion in vector path
> >
> > We may need to update the iavf.ini to claim VLAN offload is partially
> > supported to align with this implementation.
> >
> > VLAN offload = P
> I mean the vector path cannot fully support this VLAN feature. With this
> patch,
> we use scalar path instead of vector path if VLAN feature is needed. It can be
> taken as fully supported.
Ok, the "P" flag has been explained as below in iavf.ini.
A feature with "P" indicates only be supported when non-vector path is selected.
And now we just disabled VLAN insertion in vector path, right?
