In article <[EMAIL PROTECTED]> you wrote:
>> No, Dean, I think you misunderstood me here. If the shared memory
>> segment is full, I don't want to _replace_ it with a larger one. I
>> just want to _add_ another _new_ shared memory segment to the memory
>> pool and allocate the requested chunk of memory from there instead. The
>> same way a heap-based allocator uses sbrk(2) again and again to get more
>> heap segments I want to allocate more and more shared memory segments.
>
> oh i know you don't want to grow the existing segment -- but in order to
> add new segments you need to co-ordinate with all processes. you can't
> accomplish this the same way that anon-mmap() and fork() do -- you need to
> have a handle which all processes can use to open the memory. that's
> going to be a filename on unixes that don't have sysv shm...
>
> also, the rest of the problem is that all references to the shared memory
> need to be indirected -- because you can't be sure if the process you're
> running in has the segment you need mapped.
Ohhh... now I understand the point. Puuhh.. yes, correct. I've totally
overlooked these issues. Hmmm... but then: do have any chance to provide
such functionality in a portable way at all?
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
