On Wed, Sep 30, 2015 at 09:18:53AM -0400, Neil Horman wrote:
> > +}
> > diff --git a/lib/librte_ether/rte_ethdev.h b/lib/librte_ether/rte_ethdev.h
> > index fa06554..9cd262b 100644
> > --- a/lib/librte_ether/rte_ethdev.h
> > +++ b/lib/librte_ether/rte_ethdev.h
> > @@ -1635,8 +1635,23 @@ struct rte_eth_dev_data {
> > all_multicast : 1, /**< RX all multicast mode ON(1) / OFF(0). */
> > dev_started : 1, /**< Device state: STARTED(1) / STOPPED(0).
> > */
> > lro : 1; /**< RX LRO is ON(1) / OFF(0) */
> > + uint32_t dev_flags; /**< Flags controlling handling of device. */
> > + enum rte_kernel_driver kdrv; /**< Kernel driver passthrough */
> > + int numa_node;
> > + const char *drv_name;
> > };
> >
> Unrelated to my other questions on this code: Is rte_eth_dev_data ever
> allocation by any applications? If so, this will have to go through the ABI
> process. I don't think it is, but I wanted to ask to be sure
>
> Neil
>
No - applications do not allocate this structure directly, it's internal only,
so
we should be safe here from an ABI perspective.
/Bruce
