[dpdk-dev] [PATCH v3 4/4] docs: Add ABI documentation

On Tue, Dec 23, 2014 at 10:51:53AM -0500, Neil Horman wrote: > Adding a document describing rudimentary ABI policy and adding notice space > for > any deprecation announcements > > Signed-off-by: Neil Horman > CC: Thomas Monjalon > CC: "Richardson, Bruce" > --- > doc/abi.txt | 17

[dpdk-dev] [PATCH v3 3/4] Add library version extenstion

On Tue, Dec 23, 2014 at 10:51:52AM -0500, Neil Horman wrote: > To differentiate libraries that break ABI, we add a library version number > suffix to the library, which must be incremented when a given libraries ABI is > broken. This patch enforces that addition, sets the initial abi soname >

[dpdk-dev] [PATCH v3 2/4] Provide initial versioning for all DPDK libraries

On Tue, Dec 23, 2014 at 10:51:51AM -0500, Neil Horman wrote: > Add linker version script files to each DPDK library to put a stake in the > ground from which we can start cleaning up API's > > Signed-off-by: Neil Horman > CC: Thomas Monjalon > CC: "Richardson, Bruce" > > --- > Change Notes: >

[dpdk-dev] [PATCH v3 1/4] compat: Add infrastructure to support symbol versioning

On Tue, Dec 23, 2014 at 10:51:50AM -0500, Neil Horman wrote: > Add initial pass header files to support symbol versioning. > > Signed-off-by: Neil Horman > CC: Thomas Monjalon > CC: "Richardson, Bruce" > CC: "Gonzalez Monroy, Sergio" > > Change Notes: > V2) > Moved ifeq to _INSTALL

[dpdk-dev] l3fwd error, port 0 is not present on the board

On Mon, Dec 29, 2014 at 02:18:09PM -0600, Lyn M wrote: > Hello all, > > Rangeley platform (1 CPU with 8 cores, 4x1 GbE, 2x10 GbE, Intel PCIe card > with 2x10 GbE fiber) > FC20 with hugepages enabled > DPDK 1.8.0 built with T=x86_64-ivshmem-linuxapp-gcc > > */usr/src/dpdk/tools/dpdk_nic_bind.py

[dpdk-dev] l3fwd error, port 0 is not present on the board

Hello all, Rangeley platform (1 CPU with 8 cores, 4x1 GbE, 2x10 GbE, Intel PCIe card with 2x10 GbE fiber) FC20 with hugepages enabled DPDK 1.8.0 built with T=x86_64-ivshmem-linuxapp-gcc */usr/src/dpdk/tools/dpdk_nic_bind.py --status* Network devices using DPDK-compatible driver

[dpdk-dev] [PATCH 0/7] Move EAL common functions

Hi Neil, On 12/29/2014 01:47 PM, Neil Horman wrote: > On Mon, Dec 29, 2014 at 09:47:05AM +0100, Olivier MATZ wrote: >> Trying to factorize the common code goes in the good direction. >> >> However I'm wondering if "common" is the proper place. Initially, >> the common directory was for code

[dpdk-dev] [PATCH v2 1/6] Move EAL common functions

On Mon, Dec 29, 2014 at 07:34:22AM -0800, Ravi Kerur wrote: > I will change the subject and make it more explicit. In addition, I was > thinking of adding function names which are moved as part of commit message > so that it is easier for everyone to check what is moved rather than going > through

[dpdk-dev] [PATCH 0/7] Move EAL common functions

On Mon, Dec 29, 2014 at 02:16:16PM +0100, Olivier MATZ wrote: > Hi Neil, > > On 12/29/2014 01:47 PM, Neil Horman wrote: > > On Mon, Dec 29, 2014 at 09:47:05AM +0100, Olivier MATZ wrote: > >> Trying to factorize the common code goes in the good direction. > >> > >> However I'm wondering if

[dpdk-dev] [PATCH 0/7] Move EAL common functions

Thanks Olivier and Neil. I will make a note on this and will work on it after initial common code movement is completed. On Mon, Dec 29, 2014 at 5:16 AM, Olivier MATZ wrote: > Hi Neil, > > On 12/29/2014 01:47 PM, Neil Horman wrote: > > On Mon, Dec 29, 2014 at 09:47:05AM +0100, Olivier MATZ

[dpdk-dev] TSO with chained imbues

Hi Gal, On 12/25/2014 04:55 PM, Gal Sagie wrote: > Does the TSO offload option works for chained mbufs? > What i mean is, if i have a chain representing a big TCP buffer, and i only > set the first mbuf with > TSO flags and tso_segsz (mss) and L4 size, will that work ? (or only > applied on the

[dpdk-dev] [PATCH 0/7] Move EAL common functions

Hi Ravi, On 12/25/2014 04:33 PM, Ravi Kerur wrote: > Common functions in linuxapp and bsdapp are moved into > librte_eal/common directory. > New files added follow _common_ naming conventions. > Tested against ubuntu and FreeBSD. Trying to factorize the common code goes in the good direction.

[dpdk-dev] [PATCH v2] i40e: workaround for XL710 performance

On XL710, performance number is far from the expectation on recent firmware versions, if promiscuous mode is disabled, or promiscuous mode is enabled and port MAC address is equal to the packet destination MAC address. The fix for this issue may not be integrated in the following firmware version.

[dpdk-dev] [PATCH v6 5/6] enicpmd: DPDK-ENIC PMD interface

Hi, ssujith > + .tx_queue_release = enicpmd_dev_tx_queue_release, > + .dev_led_on = NULL, > + .dev_led_off = NULL, > + .flow_ctrl_get= NULL, > + .flow_ctrl_set= NULL, > + .priority_flow_ctrl_set = NULL, > + .mac_addr_add =

[dpdk-dev] [PATCH 0/7] Move EAL common functions

On Mon, Dec 29, 2014 at 09:47:05AM +0100, Olivier MATZ wrote: > Hi Ravi, > > On 12/25/2014 04:33 PM, Ravi Kerur wrote: > > Common functions in linuxapp and bsdapp are moved into > > librte_eal/common directory. > > New files added follow _common_ naming conventions. > > Tested against ubuntu and

[dpdk-dev] [PATCH v2 1/6] Move EAL common functions

I will change the subject and make it more explicit. In addition, I was thinking of adding function names which are moved as part of commit message so that it is easier for everyone to check what is moved rather than going through the patch. Do you think it would be helpful?? Thanks. On Sun, Dec