[dpdk-dev] [PATCH v2] devargs: add blacklisting by linux interface name

2015-11-10 Thread Charles (Chas) Williams
On Thu, 2015-11-05 at 11:23 -0800, Stephen Hemminger wrote: > On Thu, 05 Nov 2015 11:39:04 -0500 > "Charles (Chas) Williams" <3chas3 at gmail.com> wrote: > > > On Wed, 2015-11-04 at 23:40 +0100, Thomas Monjalon wrote: > > > 2015-10-14 09:41, Charles Williams: > > > > On Tue, 2015-10-13 at 14:49

[dpdk-dev] [PATCH v2] devargs: add blacklisting by linux interface name

2015-11-05 Thread Charles (Chas) Williams
On Wed, 2015-11-04 at 23:40 +0100, Thomas Monjalon wrote: > 2015-10-14 09:41, Charles Williams: > > On Tue, 2015-10-13 at 14:49 +0200, Olivier MATZ wrote: > > > For PCI devices that have several interfaces (I think it's the case for > > > some Mellanox boards), maybe we should not store the interf

[dpdk-dev] [PATCH v2] devargs: add blacklisting by linux interface name

2015-11-05 Thread Stephen Hemminger
On Thu, 05 Nov 2015 11:39:04 -0500 "Charles (Chas) Williams" <3chas3 at gmail.com> wrote: > On Wed, 2015-11-04 at 23:40 +0100, Thomas Monjalon wrote: > > 2015-10-14 09:41, Charles Williams: > > > On Tue, 2015-10-13 at 14:49 +0200, Olivier MATZ wrote: > > > > For PCI devices that have several

[dpdk-dev] [PATCH v2] devargs: add blacklisting by linux interface name

2015-11-04 Thread Thomas Monjalon
2015-10-14 09:41, Charles Williams: > On Tue, 2015-10-13 at 14:49 +0200, Olivier MATZ wrote: > > For PCI devices that have several interfaces (I think it's the case for > > some Mellanox boards), maybe we should not store the interface name? > > I am not sure what you mean here. If a device has

[dpdk-dev] [PATCH v2] devargs: add blacklisting by linux interface name

2015-10-14 Thread Charles (Chas) Williams
On Tue, 2015-10-13 at 14:49 +0200, Olivier MATZ wrote: > Hi Chas, > > > @@ -352,6 +354,19 @@ pci_scan_one(const char *dirname, uint16_t domain, > > uint8_t bus, > > return -1; > > } > > > > + /* get network interface name */ > > + snprintf(filename, sizeof(filename), "%s/net

[dpdk-dev] [PATCH v2] devargs: add blacklisting by linux interface name

2015-10-13 Thread Olivier MATZ
Hi Chas, On 10/05/2015 05:26 PM, Chas Williams wrote: > If a system is using deterministic interface names, it may be easier in > some cases to use the interface name to blacklist an interface. > > Signed-off-by: Chas Williams <3chas3 at gmail.com> > --- > app/test/test_devargs.c

[dpdk-dev] [PATCH v2] devargs: add blacklisting by linux interface name

2015-10-06 Thread Charles (Chas) Williams
On Tue, 2015-10-06 at 08:35 +0100, Stephen Hemminger wrote: > On Mon, 5 Oct 2015 11:26:08 -0400 > Chas Williams <3chas3 at gmail.com> wrote: > > > diff --git a/lib/librte_eal/common/include/rte_pci.h > > b/lib/librte_eal/common/include/rte_pci.h > > index 83e3c28..852c149 100644 > > --- a/lib/li

[dpdk-dev] [PATCH v2] devargs: add blacklisting by linux interface name

2015-10-06 Thread Stephen Hemminger
On Mon, 5 Oct 2015 11:26:08 -0400 Chas Williams <3chas3 at gmail.com> wrote: > diff --git a/lib/librte_eal/common/include/rte_pci.h > b/lib/librte_eal/common/include/rte_pci.h > index 83e3c28..852c149 100644 > --- a/lib/librte_eal/common/include/rte_pci.h > +++ b/lib/librte_eal/common/include/rt

[dpdk-dev] [PATCH v2] devargs: add blacklisting by linux interface name

2015-10-05 Thread Chas Williams
If a system is using deterministic interface names, it may be easier in some cases to use the interface name to blacklist an interface. Signed-off-by: Chas Williams <3chas3 at gmail.com> --- app/test/test_devargs.c | 2 ++ lib/librte_eal/common/eal_common_devargs.c | 9