2017-03-28 13:02, Van Haaren, Harry:
> > From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Gaëtan Rivet
> > On Tue, Mar 28, 2017 at 01:20:00PM +0100, Bruce Richardson wrote:
> > >On Tue, Mar 28, 2017 at 02:01:29PM +0200, Gaetan Rivet wrote:
> > >> Expects all devices to be explicitly defined bef
On Tue, Mar 28, 2017 at 01:02:13PM +, Van Haaren, Harry wrote:
If I understand correctly an app that runs without any port parameters to EAL
would now fail to find any ports?
That would result in;
- testing frameworks (DTS, fd.io perf lab, customers, etc) would fail if not
specifying ports
On Tue, Mar 28, 2017 at 02:03:48PM +0100, Bruce Richardson wrote:
On Tue, Mar 28, 2017 at 02:44:09PM +0200, Gaëtan Rivet wrote:
On Tue, Mar 28, 2017 at 01:20:00PM +0100, Bruce Richardson wrote:
> On Tue, Mar 28, 2017 at 02:01:29PM +0200, Gaetan Rivet wrote:
> > Expects all devices to be explicit
On Tue, Mar 28, 2017 at 02:44:09PM +0200, Gaëtan Rivet wrote:
> On Tue, Mar 28, 2017 at 01:20:00PM +0100, Bruce Richardson wrote:
> > On Tue, Mar 28, 2017 at 02:01:29PM +0200, Gaetan Rivet wrote:
> > > Expects all devices to be explicitly defined before being probed.
> > >
> > > The blacklist mode
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Gaëtan Rivet
> Sent: Tuesday, March 28, 2017 1:44 PM
> To: Richardson, Bruce
> Cc: dev@dpdk.org; Thomas Monjalon
> Subject: Re: [dpdk-dev] [PATCH v2 1/1] pci: default to whitelist mode
>
> On Tue, Mar 28, 2017 at 01
On Tue, Mar 28, 2017 at 01:20:00PM +0100, Bruce Richardson wrote:
On Tue, Mar 28, 2017 at 02:01:29PM +0200, Gaetan Rivet wrote:
Expects all devices to be explicitly defined before being probed.
The blacklist mode can be prone to errors, coaxing users in capturing
devices that could be used for
On Tue, Mar 28, 2017 at 02:01:29PM +0200, Gaetan Rivet wrote:
> Expects all devices to be explicitly defined before being probed.
>
> The blacklist mode can be prone to errors, coaxing users in capturing
> devices that could be used for management or otherwise.
> The whitelist mode offers users mo
Expects all devices to be explicitly defined before being probed.
The blacklist mode can be prone to errors, coaxing users in capturing
devices that could be used for management or otherwise.
The whitelist mode offers users more control and highlight mistakes by
making them visible on the command
8 matches
Mail list logo
