Hi Thomas, Sorry so long to response your email.
> -----Original Message----- > From: Thomas Monjalon <[email protected]> > Sent: Thursday, July 7, 2022 5:05 PM > To: Wu, WenxuanX <[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] > Subject: Re: [PATCH v9 1/4] ethdev: introduce protocol header API > > 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? > > > + * @return > > + * - (-ENOTSUP) if header protocol is not supported by device. > > + * - (-ENODEV) if *port_id* invalid. > > + * - (-EIO) if device is removed. > > + * - (0) on success. > > + */ > > +__rte_experimental > > +int rte_eth_supported_hdrs_get(uint16_t port_id, > > + uint32_t *ptype); > > The function name is not precise enough. > There should be the word "split" in its name. Thanks for the suggestion, it will be revised in the next version. Thanks, Yuan >
