Hi:
I haven't actually played with it, but the 'MM Shared Memory Library' at
http://www.engelschall.com/sw/mm/ looks like a starting point.
According to the manual:
"The MM library is a 2-layer abstraction library which simplifies the
usage of shared memory between forked (and this way strongly related)
processes under Unix platforms. On the first layer it hides all platform
dependent implementation details (allocation and locking) when dealing
with shared memory segments and on the second layer it provides a
high-level malloc(3)-style API for a convenient and well known way to
work with data-structures inside those shared memory segments."
BSD-style license and all that good stuff.
Regards,
- Dave
dave@codewhore.org
On Thu, Mar 21, 2002 at 04:09:51PM +0530, Amol Kumar Lad wrote:
> Hi ,
> Sorry for posting this to wrong list. But you can help me out.
>
> I am porting some code from Vxworks to Linux (application level, not
> kernel).
> THe problem is , in Vxworks as there is a single address space so a 'malloc'
> done by one process is visible to other process also, i.e. all the global
> data is shared in Vxworks across processes.
>
> This is not true in linux, as every process has its own address space.
> What could be done so that I can use same 'malloc' like interface and have
> all my 'global data'
> shared across process.
>
> I can understand that i have to use shared memory for this. Is there any
> library available
> that provides me a 'malloc' type interface for shared memory.
>
> All processes are unrelated processes ( fork -> exec)
>
> Thanks
> Amol
>
> -- please CC me..
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
This archive was generated by hypermail 2b29 : Sat Mar 23 2002 - 22:00:25 EST