[lng-odp] [Linaro/odp] 96f3c0: linux-generic: classification: implement vlan id p...

Branch: refs/heads/master Home: https://github.com/Linaro/odp Commit: 96f3c0362b61a415b9ecc319ee3427c8f4b7c081 https://github.com/Linaro/odp/commit/96f3c0362b61a415b9ecc319ee3427c8f4b7c081 Author: Balasubramanian Manoharan Date: 2017-02-10 (Fri, 10

[lng-odp] [Bug 2881] New: load sensitive tests fail on CI

https://bugs.linaro.org/show_bug.cgi?id=2881 Bug ID: 2881 Summary: load sensitive tests fail on CI Product: OpenDataPlane - linux- generic reference Version: v1.13.0.0 Hardware: Other OS: Linux Status: UNCONFIRMED

[lng-odp] Question regarding crypto block sizes and padding in ODP

Hello, I would really appreciate any comments on how ODP defines who should prepare valid data for the lower layers for encryption/decryption. Block cipher algorithms require input data to be a multiple of block size and usually to have appropriate padding. Which part of ODP is expected to

Re: [lng-odp] [PATCH 1/3] helper: cuckootable: avoid storage leaks on error paths

Reviewed and merged. Maxim. On 02/03/17 03:28, Bill Fischofer wrote: > Ensure that malloced storage areas are freed on error paths. > This resolves Bug https://bugs.linaro.org/show_bug.cgi?id=2830 > > Signed-off-by: Bill Fischofer > --- > helper/test/cuckootable.c |

[lng-odp] [Linaro/odp] 0ed479: helper: tables: avoid invalid odp_shm_addr() calls

Branch: refs/heads/master Home: https://github.com/Linaro/odp Commit: 0ed479bd9d474f1d7588f3370fb306a2e000ff4f https://github.com/Linaro/odp/commit/0ed479bd9d474f1d7588f3370fb306a2e000ff4f Author: Bill Fischofer Date: 2017-02-10 (Fri, 10 Feb 2017)

[lng-odp] [Linaro/odp] 483af9: helper: iplookuptable: removed unused variable

Branch: refs/heads/master Home: https://github.com/Linaro/odp Commit: 483af96a7a14885694496843551ed8fad708192c https://github.com/Linaro/odp/commit/483af96a7a14885694496843551ed8fad708192c Author: Bill Fischofer Date: 2017-02-10 (Fri, 10 Feb 2017)

[lng-odp] [Linaro/odp] f59d87: helper: cuckootable: avoid storage leaks on error ...

Branch: refs/heads/master Home: https://github.com/Linaro/odp Commit: f59d87a65cf1d08f8715a01dceeaf370a29e51f3 https://github.com/Linaro/odp/commit/f59d87a65cf1d08f8715a01dceeaf370a29e51f3 Author: Bill Fischofer Date: 2017-02-10 (Fri, 10 Feb 2017)

[lng-odp] [Bug 2833] dead lock in ODP-crypto on some machine

https://bugs.linaro.org/show_bug.cgi?id=2833 --- Comment #7 from Dmitry Eremin-Solenikov --- Christophe, I can not reproduce this with 32-bit chroot, Debian jessie and manually built OpenSSL 1.0.2k-fips 26 Jan 2017. Could you please be more specific about

Re: [lng-odp] ODP over PCI

Moving this discussion to the ODP mailing list. Allowing ODP-based applications running on a SmartNIC is an excellent way to accomplish two goals: 1. Allow non-ODP apps as well as the host OS itself to access SmartNIC services via a standardized mechanism. 2. Allow advanced ODP apps to divide

[lng-odp] [PATCH v3] example: add IPv4 fragmentation/reassembly example

Add an example application implementing lock-free IPv4 fragmentation and reassembly functionality using ODP's packet "concat" and "split". Signed-off-by: Joe Savage Reviewed-and-tested-by: Bill Fischofer --- (This code contribution is provided

Re: [lng-odp] Packet references API

On Fri, Feb 10, 2017 at 9:36 AM, Savolainen, Petri (Nokia - FI/Espoo) wrote: > >> > I'll send an API and validation test updates (for option 1)) with simple >> copy style implementation. >> >> It's not clear why we need a copy style implementation given that

Re: [lng-odp] [PATCH] travis: switch to ubuntu trusty

patch does work for me https://travis-ci.org/mike-holmes-linaro/odp/builds/200378657 On 10 February 2017 at 10:45, Maxim Uvarov wrote: > On 02/10/17 18:26, Mike Holmes wrote: > > > > > > On 10 February 2017 at 10:09, Maxim Uvarov >

Re: [lng-odp] [PATCH] travis: switch to ubuntu trusty

On 02/10/17 18:26, Mike Holmes wrote: > > > On 10 February 2017 at 10:09, Maxim Uvarov > wrote: > > ubuntu trusty > > > I can't see why not use trusty, it is LTS, but this implies that trusty > is the tested distro for ODP patch

Re: [lng-odp] Packet references API

> > I'll send an API and validation test updates (for option 1)) with simple > copy style implementation. > > It's not clear why we need a copy style implementation given that we > have a zero-copy implementation. While it's good to discuss this as an > option in the ODP implementation guide, as

Re: [lng-odp] [PATCH] travis: switch to ubuntu trusty

On 10 February 2017 at 10:09, Maxim Uvarov wrote: > ubuntu trusty I can't see why not use trusty, it is LTS, but this implies that trusty is the tested distro for ODP patch acceptance. Do we need to update CONTRIBUTING to say that this version does define the pass

[lng-odp] [PATCH] travis: switch to ubuntu trusty

ubuntu trusty has updated doxygen 1.8.4 which match your requirements and do not generate any warnings. Also no need to compile cunit anymore we can take it from packages. Compiler version stays the same 4.8 for gcc. Signed-off-by: Maxim Uvarov --- .travis.yml | 21

Re: [lng-odp] [PATCH 1/2] helper: linux: renamed threads_extn to linux helpers

On 3 February 2017 at 06:23, Petri Savolainen wrote: > There's no platform specific helpers. Helpers may depend on > Linux and make it easier to do common series of Linux system > calls. These kind of helpers are grouped into helper/linux > directory. > > Use

[lng-odp] [PATCH] configure: libatomic check

upcoming patch ip fragmentation example fails to with gcc 4.8.4 on linking __atomic_compare_exchange_16 functions on x86. Both -latomic and -mcx16 needs to be provided in that case. This patch adds additional checks to find combination of required -latomic and -mcx16 options. Signed-off-by: Maxim

Re: [lng-odp] Packet references API

On Fri, Feb 10, 2017 at 6:24 AM, Savolainen, Petri (Nokia - FI/Espoo) wrote: > > >> -Original Message- >> From: Bill Fischofer [mailto:bill.fischo...@linaro.org] >> Sent: Friday, February 10, 2017 12:46 AM >> To: Savolainen, Petri (Nokia - FI/Espoo)

Re: [lng-odp] driver probe time...

The purpose of odp_init_global() and odp_init_local() (as well as the corresponding global and local term routines) is to provide a conceptual "bracket" around application use of ODP APIs and services. The ODP spec itself does not say what goes on in these APIs--that is up to each implementation.

Re: [lng-odp] Packet references API

> -Original Message- > From: Bill Fischofer [mailto:bill.fischo...@linaro.org] > Sent: Friday, February 10, 2017 12:46 AM > To: Savolainen, Petri (Nokia - FI/Espoo) labs.com> > Cc: lng-odp@lists.linaro.org > Subject: Re: [lng-odp] Packet references API >

Re: [lng-odp] [PATCH v2] example: add IPv4 fragmentation/reassembly example

> what happens if you add libatomic in configure on your system? > ./configure CFLAGS="-latomic" > > > does it fail that there is no such lib? That works fine for me. But, on the x86 and ARM machines I have to hand, everything also works perfectly without this additional flag. This is what I

Re: [lng-odp] [PATCH v2] example: add IPv4 fragmentation/reassembly example

what happens if you add libatomic in configure on your system? ./configure CFLAGS="-latomic" does it fail that there is no such lib? On 10 February 2017 at 13:31, Joe Savage wrote: > Thanks, Maxim. Assuming that's the last of the additional comments, I think > I've

Re: [lng-odp] [PATCH v2] example: add IPv4 fragmentation/reassembly example

Thanks, Maxim. Assuming that's the last of the additional comments, I think I've cleaned everything up ready for v3. That is, besides the potential issue with libatomic. > > +/** > > + * Clean up any stale flows within a fraglist > > + * > > + * @param fl Pointer to the shared fraglist to

[lng-odp] driver probe time...

Hi, I am facing a issue: When should driver elements (enumerators-classes, enumerators, drivers) be probed at startup: My initial idea was to perform probing at init global time, so that a starting app would have a chance to see the present interfaces at startup: This turns out to be a problem as