Yes. Support for shm created outside ODP will cause a lot of overhead.
we can use IPC mechanism to check the validity of the allocated shm in ODP
from a non-ODP process.

@Maxim
Sure.I will continue the IPC discussion in IPC patch.

Regards,
Bala


On 8 September 2014 13:10, Savolainen, Petri (NSN - FI/Espoo) <
[email protected]> wrote:

>
>
> > -----Original Message-----
> > From: [email protected] [mailto:lng-odp-
> > [email protected]] On Behalf Of ext Maxim Uvarov
> > Sent: Monday, September 08, 2014 9:31 AM
> > To: Bala Manoharan
> > Cc: lng-odp-forward
> > Subject: Re: [lng-odp] [PATCH v2 1/2] Shared memory reserve flag
> >
> > On 09/08/2014 09:30 AM, Bala Manoharan wrote:
> > > Hi,
> > >
> > > A Few queries from my side,
> > >
> > > * ODP_SHM_PROC: In this case we need a mechanism to allow ODP process
> > > to be able to do a lookup of shared memory created by process outside
> > > of ODP. Current odp_shm_lookup only checks shm created by ODP process.
> >
> > Yes. And this is process odp_shm_reserve(). You can take a look how I do
> > it for IPC in ipc patches. You need to call odp_shm_reserve() in 2
> > process with the same "name" argument.
>
> Do we want to support shm created outside of ODP? Since ODP does not have
> full control over that memory, ODP cannot guarantee that application can
> use it in a portable way. Maybe it's better to operate such memory outside
> of ODP.
>
> If decided to support in ODP, it should be clearly separate from ODP
> controlled shm.
>
> -Petri
>
>
>
>
_______________________________________________
lng-odp mailing list
[email protected]
http://lists.linaro.org/mailman/listinfo/lng-odp

Reply via email to