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 processes can be linked with the ODP lib. Is it used anywhere?. thx, Christophe
On 11 February 2016 at 15:28, Christophe Milard < christophe.mil...@linaro.org> wrote: > 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. linux syscall)? (meaning that each ODP > implementation have to document how to do that) > > > On 11 February 2016 at 14:35, Christophe Milard < > christophe.mil...@linaro.org> wrote: > >> 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 there to really get >> SHARED mem between ODP threads?? >> >> This was definitively not my understanding.... >> >> I though the flag was to make the memory reachable from non-odp >> processes... >> >> Petri, What is your view? >> >> Thanks (both of you) >> >> Christophe. >> >> >> On 10 February 2016 at 19:17, Maxim Uvarov <maxim.uva...@linaro.org> >> wrote: >> >>> 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 with the ODP lib and however remain non ODP) >>>> - or the native OS (e.g. linux syscall)? (meaning that each ODP >>>> implementation have to document how to do that) >>>> >>>> Thanks, >>>> >>>> Christophe. >>>> >>> >>> No. That is flag to odp_shm_reserve saying that allocated memory should >>> be visible by 2 different processes. >>> >>> Maxim. >>> >>> >>>> >>>> _______________________________________________ >>>> lng-odp mailing list >>>> lng-odp@lists.linaro.org >>>> https://lists.linaro.org/mailman/listinfo/lng-odp >>>> >>> >>> _______________________________________________ >>> lng-odp mailing list >>> lng-odp@lists.linaro.org >>> https://lists.linaro.org/mailman/listinfo/lng-odp >>> >> >> >
_______________________________________________ lng-odp mailing list lng-odp@lists.linaro.org https://lists.linaro.org/mailman/listinfo/lng-odp
