Re: [dpdk-dev] [PATCH v3 3/8] devargs: introduce insert function

2017-07-13 Thread Jan Blunck
On Wed, Jul 12, 2017 at 1:20 PM, Gaëtan Rivet wrote: > On Wed, Jul 12, 2017 at 04:20:48AM -0400, Jan Blunck wrote: >> On Tue, Jul 11, 2017 at 7:25 PM, Gaetan Rivet wrote: >> > Some buses will operate either in whitelist or blacklist mode. >> > This mode is currently passed down by the rte_eal_dev

Re: [dpdk-dev] [PATCH v3 3/8] devargs: introduce insert function

2017-07-12 Thread Gaëtan Rivet
On Wed, Jul 12, 2017 at 04:20:48AM -0400, Jan Blunck wrote: > On Tue, Jul 11, 2017 at 7:25 PM, Gaetan Rivet wrote: > > Some buses will operate either in whitelist or blacklist mode. > > This mode is currently passed down by the rte_eal_devargs_add function > > with the devtype argument. > > > > Wh

Re: [dpdk-dev] [PATCH v3 3/8] devargs: introduce insert function

2017-07-12 Thread Jan Blunck
On Tue, Jul 11, 2017 at 7:25 PM, Gaetan Rivet wrote: > Some buses will operate either in whitelist or blacklist mode. > This mode is currently passed down by the rte_eal_devargs_add function > with the devtype argument. > > When inserting devices using the hotplug API, the implicit assumption is >

[dpdk-dev] [PATCH v3 3/8] devargs: introduce insert function

2017-07-11 Thread Gaetan Rivet
Some buses will operate either in whitelist or blacklist mode. This mode is currently passed down by the rte_eal_devargs_add function with the devtype argument. When inserting devices using the hotplug API, the implicit assumption is that this device is being whitelisted, meaning that it is explic