Re: [lng-odp] ODP_SHM_PROC shmem flag

2016-02-11 Thread Maxim Uvarov
On 02/11/16 12:10, Savolainen, Petri (Nokia - FI/Espoo) wrote: -Original Message- From: lng-odp [mailto:lng-odp-boun...@lists.linaro.org] On Behalf Of EXT Maxim Uvarov Sent: Wednesday, February 10, 2016 8:17 PM To: lng-odp@lists.linaro.org Subject: Re: [lng-odp] ODP_SHM_PROC shmem flag

Re: [lng-odp] ODP_SHM_PROC shmem flag

2016-02-11 Thread Savolainen, Petri (Nokia - FI/Espoo)
> -Original Message- > From: lng-odp [mailto:lng-odp-boun...@lists.linaro.org] On Behalf Of EXT > Maxim Uvarov > Sent: Wednesday, February 10, 2016 8:17 PM > To: lng-odp@lists.linaro.org > Subject: Re: [lng-odp] ODP_SHM_PROC shmem flag > > On 02/10/2016 20:43,

Re: [lng-odp] ODP_SHM_PROC shmem flag

2016-02-11 Thread Christophe Milard
Hi, Petri: Do you know which interface the non-ODP process is supposed to be using? shall it use odp_shm_lookup() and odp_shm_addr() or -in linux case- shm_open() +mmap? The first alternative implies that each plarform must document the method to be used. The second method implies that non-ODP

Re: [lng-odp] ODP_SHM_PROC shmem flag

2016-02-11 Thread Savolainen, Petri (Nokia - FI/Espoo)
> -Original Message- > From: EXT Maxim Uvarov [mailto:maxim.uva...@linaro.org] > Sent: Thursday, February 11, 2016 11:20 AM > To: Savolainen, Petri (Nokia - FI/Espoo) <petri.savolai...@nokia.com>; > lng-odp@lists.linaro.org > Subject: Re: [lng-odp] ODP_SHM_PROC

Re: [lng-odp] ODP_SHM_PROC shmem flag

2016-02-11 Thread Christophe Milard
OK. So my first understanding was correct. So I am back to my original question: through which interface should the non-ODP process reach the shared mem? - the ODP API? (which means that non ODP processes/thread could be linked with the ODP lib and however remain non ODP) - or the native OS (e.g.

Re: [lng-odp] ODP_SHM_PROC shmem flag

2016-02-11 Thread Christophe Milard
I don't understand here... My understanding is that shmem_reserve would always allocate SHARED memory, i.e. at least visible by all ODP processes (even with no flag). Are you saying, Maxim, that shmem_reserve() should allocate thread-local memory when no flag is set and that the ODP_SHM_PROC is

[lng-odp] ODP_SHM_PROC shmem flag

2016-02-10 Thread Christophe Milard
Hi, If I understand correctly, the usage of this flag tells that Non ODP processes/thread can gain access to the shared memory. My question is: through which interface? - the ODP API? (which means that non ODP processes/thread could be linked with the ODP lib and however remain non ODP) - or the

Re: [lng-odp] ODP_SHM_PROC shmem flag

2016-02-10 Thread Maxim Uvarov
On 02/10/2016 20:43, Christophe Milard wrote: Hi, If I understand correctly, the usage of this flag tells that Non ODP processes/thread can gain access to the shared memory. My question is: through which interface? - the ODP API? (which means that non ODP processes/thread could be linked