Hi Thomas,

> -----Original Message-----
> From: Thomas Monjalon <[email protected]>
> Sent: Monday, August 1, 2022 6:01 PM
> To: Wang, YuanX <[email protected]>
> Cc: [email protected]; Li, Xiaoyun <[email protected]>;
> [email protected]; Singh, Aman Deep <[email protected]>;
> [email protected]; Zhang, Yuying <[email protected]>; Zhang, Qi Z
> <[email protected]>; [email protected];
> [email protected]; Wu, WenxuanX <[email protected]>;
> Ding, Xuan <[email protected]>
> Subject: Re: [PATCH v9 1/4] ethdev: introduce protocol header API
> 
> 01/08/2022 09:09, Wang, YuanX:
> > Hi Thomas,
> >
> > Sorry so long to response your email.
> >
> > From: Thomas Monjalon <[email protected]>
> > > 13/06/2022 12:25, [email protected]:
> > > > From: Wenxuan Wu <[email protected]>
> > > >
> > > > This patch added new ethdev API to retrieve supported protocol
> > > > header mask of a PMD, which helps to configure protocol header based
> buffer split.
> > > >
> > > > Signed-off-by: Wenxuan Wu <[email protected]>
> > > > ---
> > > > +/**
> > > > + * @warning
> > > > + * @b EXPERIMENTAL: this API may change without prior notice
> > > > + *
> > > > + * Get supported header protocols to split supported by PMD.
> > > > + * The API will return error if the device is not valid.
> > > > + *
> > > > + * @param port_id
> > > > + *   The port identifier of the device.
> > > > + * @param ptype
> > > > + *   Supported protocol headers of driver.
> > >
> > > It doesn't say where to find the types.
> > > Please give the prefix.
> >
> > Sorry I didn't catch your point, are you referring the ptype should be
> composed of RTE_PTYPE_*?
> > Could you explain it in more detail?
> 
> Yes just give to the user the required info to use the function.
> If ptype must be composed with RTE_PTYPE_*, it must be said.

Thanks for your explanation, will fix in the next version.

Thanks,
Yuan

> 
> Thanks
> 

Reply via email to