[lng-odp] [PATCH] linux-generic: Add ARM odp_cpu_pause()

Signed-off-by: Brian Brooks --- platform/linux-generic/arch/arm/odp/api/cpu_arch.h | 6 ++ 1 file changed, 6 insertions(+) diff --git a/platform/linux-generic/arch/arm/odp/api/cpu_arch.h b/platform/linux-generic/arch/arm/odp/api/cpu_arch.h index 22b1da2d..7c75a690 100644 --- a/platform/linu

Re: [lng-odp] [API-NEXT PATCH] linux-gen: support older libconfig version

tested here: https://travis-ci.org/muvarov/odp/builds/195670579 On 01/27/17 00:11, Maxim Uvarov wrote: > Travis CI uses old libconfig8 amd64 1.3.2-2ubuntu2, > which does not have defines for errors. Move error print > under ifdef to fix compilation. > > Signed-off-by: Maxim Uvarov > --- > platf

Re: [lng-odp] schedule_multi returning tasks from multiple queues

On Wed, Jan 25, 2017 at 11:13 PM, Honnappa Nagarahalli wrote: > I agree, it needs additional operations. One could combine multiple > atomic operations into a single stage where possible. If the scheduler > is implemented in hardware, impact will be less. > > The other option is for the reordering

Re: [lng-odp] [openfastpath] Performance issues found in OFP 2.0 upon integration into Memcached

On Thu, Jan 26, 2017 at 8:14 AM, Peltonen, Janne (Nokia - FI/Espoo) wrote: > Hi, > >> > I took a look at the default_event_dispatcher() in OFP v2.0 code and >> > noticed >> > that it calls odp_schedule_multi() and it blocks until it receives the >> > burst size. >> > This will likely cause the s

Re: [lng-odp] [PATCH v3 0/8] First ABI files

On 01/26 10:16:11, Petri Savolainen wrote: > Added initial version of couple of ABI specification files. These files > define > types/values that are implementation specific in the API spec. For ABI > compatibility, application and implementation need to use these definitions > (based on the ta

[lng-odp] [Bug 2857] Bus error on not enough hdd space (Ubuntu VM, aarch64)

https://bugs.linaro.org/show_bug.cgi?id=2857 --- Comment #3 from Bill Fischofer --- OK, if /dev/shm is the standard place for this and doesn't pose any sudo requirements, then we should do that and configurability on this becomes a much lower priority (probably not needed). -- You are receiving

Re: [lng-odp] [PATCH v4 3/4] helper: move thread implementation under platform

On 23 January 2017 at 10:17, Savolainen, Petri (Nokia - FI/Espoo) < petri.savolai...@nokia-bell-labs.com> wrote: > > > > -Original Message- > > From: Mike Holmes [mailto:mike.hol...@linaro.org] > > Sent: Monday, January 23, 2017 3:01 PM > > To: Savolainen, Petri (Nokia - FI/Espoo) > labs.

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

On 01/26/17 18:27, Ola Liljedahl wrote: > > > On 26 January 2017 at 15:19, Joe Savage > wrote: > > > >> It will be very helpful if rehe was some README with description > about > > >> this app, run environments and some output. So people can learn > > >>

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

On 26 January 2017 at 15:19, Joe Savage wrote: > > >> It will be very helpful if rehe was some README with description about > > >> this app, run environments and some output. So people can learn > > >> something before looking to code. > > > > > > I can add one, but I don't think there's really

[lng-odp] [Bug 2857] Bus error on not enough hdd space (Ubuntu VM, aarch64)

https://bugs.linaro.org/show_bug.cgi?id=2857 --- Comment #2 from Maxim Uvarov --- yes, they can. Actually shm_open() call also creates file in /dev/shm. It's tmpfs which available for users. I usually use it to speed up compilation :) -- You are receiving this mail because: You are on the CC li

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

On 01/26/17 17:26, Joe Savage wrote: >>> we used MAX_WORKERS before odp_cpumask_default_worker() was implemented, >>> after that we did not rewrite old example. I think it's better to have >>> less defines in code. >> >> Ok, will do. > > Actually, scratch that. MAX_WORKERS is also used allocate th

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

> > we used MAX_WORKERS before odp_cpumask_default_worker() was implemented, > > after that we did not rewrite old example. I think it's better to have > > less defines in code. > > Ok, will do. Actually, scratch that. MAX_WORKERS is also used allocate the correct number of elements in the thread

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

> >> It will be very helpful if rehe was some README with description about > >> this app, run environments and some output. So people can learn > >> something before looking to code. > > > > I can add one, but I don't think there's really that much to describe. Since > > the example doesn't conne

Re: [lng-odp] [openfastpath] Performance issues found in OFP 2.0 upon integration into Memcached

Hi, > > I took a look at the default_event_dispatcher() in OFP v2.0 code and noticed > > that it calls odp_schedule_multi() and it blocks until it receives the > > burst size. > > This will likely cause the starvation issues Bill mentioned. I am not sure about that. The dispatcher calls odp_sche

Re: [lng-odp] [openfastpath] Performance issues found in OFP 2.0 upon integration into Memcached

On Thu, Jan 26, 2017 at 6:55 AM, Geoffrey Blake wrote: > I will reiterate that I am using OFP and ODP in ways that were not originally > intended and the problems I have exposed are in a way unique to that usage. > But the problem with batching is still relevant. I took a look at the > defaul

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

On 01/26/17 14:01, Joe Savage wrote: > Thanks, Maxim. Just a few things... > >> It will be very helpful if rehe was some README with description about >> this app, run environments and some output. So people can learn >> something before looking to code. > > I can add one, but I don't think there

Re: [lng-odp] [openfastpath] Performance issues found in OFP 2.0 upon integration into Memcached

I will reiterate that I am using OFP and ODP in ways that were not originally intended and the problems I have exposed are in a way unique to that usage. But the problem with batching is still relevant. I took a look at the default_event_dispatcher() in OFP v2.0 code and noticed that it calls

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

> > + return __atomic_compare_exchange_16(var, exp, neu, false, > > mo_success, > > + mo_failure); > > This is the line that clang complains about. You're probably more > expert than I in this area but the _odp_atomic_u128_xchg_mm() routine > that O

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

Thanks, Maxim. Just a few things... > It will be very helpful if rehe was some README with description about > this app, run environments and some output. So people can learn > something before looking to code. I can add one, but I don't think there's really that much to describe. Since the examp

[lng-odp] [PATCH v3 3/8] abi: classifier: added initial definitions

Initially, use the same default ABI file for all architectures. Default values match those defined in odp-linux implementation to minimize changes in this phase. Removed unused type definitions, documentation of those need to be still removed for API spec. Signed-off-by: Petri Savolainen --- ...

[lng-odp] [PATCH v3 0/8] First ABI files

Added initial version of couple of ABI specification files. These files define types/values that are implementation specific in the API spec. For ABI compatibility, application and implementation need to use these definitions (based on the target architecture). ABI is defined by CPU ISA (includi

[lng-odp] [PATCH v3 1/8] abi: event: added the first ABI spec file

Used event API as the first example of an ABI spec file. Used the same default architecture file initially for all architectures. Default ABI files avoid multiple copies of the same definition. Signed-off-by: Petri Savolainen --- configure.ac | 22 ++

[lng-odp] [PATCH v3 2/8] abi: buffer: added initial definitions

Initially, use the same default ABI file for all architectures. Default values match those defined in odp-linux implementation to minimize changes in this phase. Signed-off-by: Petri Savolainen --- include/odp/arch/arm32-linux/odp/api/abi/buffer.h | 7 include/odp/arch/arm64-linux/odp/api

[lng-odp] [PATCH v3 7/8] abi: queue: added initial definitions

Initially, use the same default ABI file for all architectures. Default values match those defined in odp-linux implementation to minimize changes in this phase. Removed an unused type definition, documentation of that need to be still removed for API spec. Moved a TM specific define into TM source

[lng-odp] [PATCH v3 6/8] abi: pool: added initial definitions

Initially, use the same default ABI file for all architectures. Default values match those defined in odp-linux implementation to minimize changes in this phase. Signed-off-by: Petri Savolainen --- example/timer/odp_timer_test.c | 2 +- include/odp/arch/arm32-linux/odp/api/a

[lng-odp] [PATCH v3 4/8] abi: crypto: added initial definitions

Initially, use the same default ABI file for all architectures. Default values match those defined in odp-linux implementation to minimize changes in this phase. Signed-off-by: Petri Savolainen --- include/odp/arch/arm32-linux/odp/api/abi/crypto.h | 7 + include/odp/arch/arm64-linux/odp/ap

[lng-odp] [PATCH v3 8/8] abi: shm: added initial definitions

Initially, use the same default ABI file for all architectures. Default values match those defined in odp-linux implementation to minimize changes in this phase. Signed-off-by: Petri Savolainen --- .../arch/arm32-linux/odp/api/abi/shared_memory.h | 7 + .../arch/arm64-linux/odp/api/abi/sh

[lng-odp] [PATCH v3 5/8] abi: packet: added initial definitions

Initially, use the same default ABI file for all architectures. Default values match those defined in odp-linux implementation to minimize changes in this phase. Signed-off-by: Petri Savolainen --- include/odp/arch/arm32-linux/odp/api/abi/packet.h | 7 include/odp/arch/arm64-linux/odp/api