Re: [lng-odp] [API-NEXT PATCHv6 05/13] api: shm: add flags to shm_reserve and function to find external mem

2016-11-17 Thread Savolainen, Petri (Nokia - FI/Espoo)
> -Original Message- > From: lng-odp [mailto:lng-odp-boun...@lists.linaro.org] On Behalf Of > Christophe Milard > Sent: Monday, October 31, 2016 10:52 AM > To: mike.hol...@linaro.org; bill.fischo...@linaro.org; lng- > o...@lists.linaro.org > Subject: [lng-odp] [API-NEXT PATCHv6 05/13]

Re: [lng-odp] [API-NEXT PATCHv6 05/13] api: shm: add flags to shm_reserve and function to find external mem

2016-10-31 Thread Christophe Milard
don't agree, as this is not a lookup. That was the confusion I was trying to avoid by having it as a reserve_*) function... This one allocates a new handles, and therefore needs a free(). In my eyes, the former name, reserve_exoprted() was better, but Petri nacked it. On 31 October 2016 at

Re: [lng-odp] [API-NEXT PATCHv6 05/13] api: shm: add flags to shm_reserve and function to find external mem

2016-10-31 Thread Maxim Uvarov
Petri, please review API patch. On 10/31/16 11:52, Christophe Milard wrote: The ODP_SHM_SINGLE_VA flag is created: when set (at odp_shm_reserve()), this flag guarantees that all ODP threads sharing this memory block will see the block at the same address (regadless of ODP thread type -pthread

[lng-odp] [API-NEXT PATCHv6 05/13] api: shm: add flags to shm_reserve and function to find external mem

2016-10-31 Thread Christophe Milard
The ODP_SHM_SINGLE_VA flag is created: when set (at odp_shm_reserve()), this flag guarantees that all ODP threads sharing this memory block will see the block at the same address (regadless of ODP thread type -pthread vs process- or fork time) The flag ODP_SHM_EXPORT is added: when passed at