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.
> >
> > A device class is the northbound interface of the device, intended
> > for applications to know what it can be used for.
> >
> > It is conceptually just above buses.
> >
> > Signed-off-by: Gaetan Rivet <gaetan.ri...@6wind.com>
> > ---
>
> [...]
>
> > --- a/lib/librte_eal/rte_eal_version.map
> > +++ b/lib/librte_eal/rte_eal_version.map
> > @@ -244,6 +244,8 @@ DPDK_18.05 {
> > EXPERIMENTAL {
> > global:
> > + rte_class_register;
> > + rte_class_unregister;
> > rte_ctrl_thread_create;
> > rte_dev_event_callback_register;
> > rte_dev_event_callback_unregister;
> >
>
> 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 for catching this, I
think it should be exposed and tagged experimental.
--
Gaëtan Rivet
6WIND
