[dpdk-dev] [PATCH 1/2] bnx2x: fix error handling in bnx2x_loop_obtain_resources()

2016-02-08 Thread Charles (Chas) Williams
I am afraid I don't understand what you are asking. This was broken in the commit that added bnx2x, 540a211084a7695a1c7bc43068934c140d6989be On 02/08/2016 05:51 AM, Bruce Richardson wrote: > On Wed, Dec 30, 2015 at 07:37:50PM -0500, Chas Williams wrote: >> From: "Charles (

[dpdk-dev] [PATCH] bnx2x: set Ethernet address type during transmit for VF's

2015-12-08 Thread Charles (Chas) Williams
On Mon, 2015-12-07 at 17:29 +, Harish Patil wrote: > > > >On Sun, 2015-12-06 at 23:34 +, Harish Patil wrote: > >> > > >> >The original was always setting unicast. While here, clean up some > >> >other references that also point into the Ethernet header. > >> > > >> >Signed-off-by: Chas

[dpdk-dev] [PATCH] bnx2x: set Ethernet address type during transmit for VF's

2015-12-07 Thread Charles (Chas) Williams
On Sun, 2015-12-06 at 23:34 +, Harish Patil wrote: > > > >The original was always setting unicast. While here, clean up some > >other references that also point into the Ethernet header. > > > >Signed-off-by: Chas Williams <3chas3 at gmail.com> > >--- > > drivers/net/bnx2x/bnx2x.c | 23

[dpdk-dev] [PATCH] bnx2x: tx_start_bd->vlan_or_ethertype is le16

2015-12-02 Thread Charles (Chas) Williams
On Wed, 2015-12-02 at 02:04 +0100, Thomas Monjalon wrote: > 2015-12-01 18:58, Charles Williams: > > On Wed, 2015-12-02 at 00:34 +0100, Thomas Monjalon wrote: > > > 2015-12-01 14:37, Stephen Hemminger: > > > > Harish Patil wrote: > > > > > >2015-11-03 12:26, Chas Williams: > > > > > >> ---

[dpdk-dev] [PATCH] bnx2x: tx_start_bd->vlan_or_ethertype is le16

2015-12-01 Thread Charles (Chas) Williams
On Wed, 2015-12-02 at 00:34 +0100, Thomas Monjalon wrote: > 2015-12-01 14:37, Stephen Hemminger: > > Harish Patil wrote: > > > >2015-11-03 12:26, Chas Williams: > > > >> --- a/drivers/net/bnx2x/bnx2x.c > > > >> +++ b/drivers/net/bnx2x/bnx2x.c > > > >> -

[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 Will

[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

[dpdk-dev] Status of bnx2x pmd?

2015-11-04 Thread Charles (Chas) Williams
On Fri, 2015-10-30 at 18:10 -0400, Mussar, Gary wrote: > I have been attempting to build testpmd with the bnx2x pmd enabled to try and > talk through a bcm57810 10G NIC card. I have tried using SR-IOV VFs and I > have tried using the PFs. Neither seem to be able to be properly initialized > in

[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),

[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 > > ---

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

2015-10-05 Thread Charles (Chas) Williams
On Fri, 2015-10-02 at 16:44 +, Richardson, Bruce wrote: > I'm not sure about that, to be honest. However, I'd rather not have > too many cmd line options to be maintained in the code. > > Does you proposed blacklisting patch work with non-pci devices as well > as with PCI ones as now? I

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

2015-10-02 Thread Charles (Chas) Williams
On Fri, 2015-10-02 at 16:44 +, Richardson, Bruce wrote: > > -Original Message- > > From: Charles (Chas) Williams [mailto:3chas3 at gmail.com] > > > > On Fri, 2015-10-02 at 16:18 +0100, Bruce Richardson wrote: > > > On Fri, Oct 02, 2015 at 11:0

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

2015-10-02 Thread Charles (Chas) Williams
On Fri, 2015-10-02 at 16:18 +0100, Bruce Richardson wrote: > On Fri, Oct 02, 2015 at 11:00:07AM -0400, 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. > > > > Is it possible to do