On Mon, Oct 04, 1999 at 12:41:45PM +0200, Stas Bekman wrote:
> > Preloading has nothing todo with shared memory. The idea is to load as much
> > as possible in the parent process. Now, when a child is forked, all childs
> > have the same modules loaded. Since Unix only copies the memory when a wri
> > Preloading has nothing todo with shared memory. The idea is to load as
much
> > as possible in the parent process. Now, when a child is forked, all
childs
> > have the same modules loaded. Since Unix only copies the memory when a
write
> > to a memory loactaion takes place, the preloaded mod
> Preloading has nothing todo with shared memory. The idea is to load as much
> as possible in the parent process. Now, when a child is forked, all childs
> have the same modules loaded. Since Unix only copies the memory when a write
> to a memory loactaion takes place, the preloaded modules will
actually share
the same memory location, as long as they not write to the memory.
Gerald
- Original Message -
From: randyboy <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Sonntag, 3. Oktober 1999 23:15
Subject: using shared memory.
> hi,
>
> so, i read all this stu
hi,
so, i read all this stuff about using shared memory, preloading stuff to
each child doesn't have it's own copy. so i went ahead and compile sysV
shared memory into my kernel. however, ipcs tells me that nothing is
using shared memory:
server# ipcs -m
Shared Memory:
T
