12/07/2018 09:41, Gaëtan Rivet:
> On Thu, Jul 12, 2018 at 12:19:09PM +0530, Shreyansh Jain wrote:
> > Any reason you don't want the rte_class_find and rte_class_find_by_name as
> > exposed APIs? There is no experimental tag on these APIs either.
>
> No actually I just overlooked that part! Thanks
Hi,
Some doxygen parameters must be fixed.
See below:
11/07/2018 23:44, Gaetan Rivet:
> +/**
> + * Register a Class handle.
> + *
> + * @param
> + * A pointer to a rte_class structure describing the class
> + * to be registered.
> + */
> +__rte_experimental
> +void rte_class_register(struct r
On Thu, Jul 12, 2018 at 12:19:09PM +0530, Shreyansh Jain wrote:
> On Thursday 12 July 2018 03:14 AM, Gaetan Rivet wrote:
> > This abstraction exists since the infancy of DPDK.
> > It needs to be fleshed out however, to allow a generic
> > description of devices properties and capabilities.
> >
> >
On Thursday 12 July 2018 03:14 AM, Gaetan Rivet wrote:
This abstraction exists since the infancy of DPDK.
It needs to be fleshed out however, to allow a generic
description of devices properties and capabilities.
A device class is the northbound interface of the device, intended
for applications
This abstraction exists since the infancy of DPDK.
It needs to be fleshed out however, to allow a generic
description of devices properties and capabilities.
A device class is the northbound interface of the device, intended
for applications to know what it can be used for.
It is conceptually jus
5 matches
Mail list logo
