Re: [RFC v3 21/26] bus: hide bus object

2022-07-29 Thread David Marchand
On Fri, Jul 29, 2022 at 12:02 PM Bruce Richardson wrote: > However, if we do look to fix, how about just dropping the runtime check > completely and just using a build-time one for the RTE_NET_RING macro. I > don't consider it valid for the tests to run with some of the built drivers > deleted. If

Re: [RFC v3 21/26] bus: hide bus object

2022-07-29 Thread Bruce Richardson
On Thu, Jul 28, 2022 at 09:26:16PM +0200, David Marchand wrote: > On Thu, Jul 28, 2022 at 6:57 PM Bruce Richardson > wrote: > > > > On Thu, Jul 28, 2022 at 05:26:35PM +0200, David Marchand wrote: > > > Make rte_bus opaque for non internal users. > > > This will make extending this object possible

Re: [RFC v3 21/26] bus: hide bus object

2022-07-28 Thread David Marchand
On Thu, Jul 28, 2022 at 6:57 PM Bruce Richardson wrote: > > On Thu, Jul 28, 2022 at 05:26:35PM +0200, David Marchand wrote: > > Make rte_bus opaque for non internal users. > > This will make extending this object possible without breaking the ABI. > > > > Introduce a new driver header and move rte

Re: [RFC v3 21/26] bus: hide bus object

2022-07-28 Thread Bruce Richardson
On Thu, Jul 28, 2022 at 05:26:35PM +0200, David Marchand wrote: > Make rte_bus opaque for non internal users. > This will make extending this object possible without breaking the ABI. > > Introduce a new driver header and move rte_bus definition and helpers. > Update drivers and library to use the

[RFC v3 21/26] bus: hide bus object

2022-07-28 Thread David Marchand
Make rte_bus opaque for non internal users. This will make extending this object possible without breaking the ABI. Introduce a new driver header and move rte_bus definition and helpers. Update drivers and library to use the internal header. Some applications may have been dereferencing rte_bus o