Re: [dpdk-dev] [PATCH 1/8] eal: expose rte_eal_using_phys_addrs

2017-07-03 Thread Olivier Matz
On Mon, 3 Jul 2017 12:04:37 +0200, Jan Blunck wrote: > On Mon, Jul 3, 2017 at 10:25 AM, Olivier Matz wrote: > > Hi, > > > > On Fri, 30 Jun 2017 21:05:47 +0200, Jan Blunck > > wrote: > >> On Thu, Jun 1, 2017 at 12:14 PM, Gaetan Rivet > >> wrote: > >> > This function was previously private

Re: [dpdk-dev] [PATCH 1/8] eal: expose rte_eal_using_phys_addrs

2017-07-03 Thread Jan Blunck
On Mon, Jul 3, 2017 at 10:25 AM, Olivier Matz wrote: > Hi, > > On Fri, 30 Jun 2017 21:05:47 +0200, Jan Blunck wrote: >> On Thu, Jun 1, 2017 at 12:14 PM, Gaetan Rivet wrote: >> > This function was previously private to the EAL layer. >> > Other subsystems requires it, such as the PCI bus. >> > >>

Re: [dpdk-dev] [PATCH 1/8] eal: expose rte_eal_using_phys_addrs

2017-07-03 Thread Olivier Matz
Hi, On Fri, 30 Jun 2017 21:05:47 +0200, Jan Blunck wrote: > On Thu, Jun 1, 2017 at 12:14 PM, Gaetan Rivet wrote: > > This function was previously private to the EAL layer. > > Other subsystems requires it, such as the PCI bus. > > > > This function is only exposed for linuxapps. > > > > In order

Re: [dpdk-dev] [PATCH 1/8] eal: expose rte_eal_using_phys_addrs

2017-06-30 Thread Jan Blunck
On Thu, Jun 1, 2017 at 12:14 PM, Gaetan Rivet wrote: > This function was previously private to the EAL layer. > Other subsystems requires it, such as the PCI bus. > > This function is only exposed for linuxapps. > > In order not to force other components to include stdbool, which is > incompatible

[dpdk-dev] [PATCH 1/8] eal: expose rte_eal_using_phys_addrs

2017-06-01 Thread Gaetan Rivet
This function was previously private to the EAL layer. Other subsystems requires it, such as the PCI bus. This function is only exposed for linuxapps. In order not to force other components to include stdbool, which is incompatible with several NIC drivers, the return type has been changed from b