> Another factor, not under our control, is that if the shared memory
> region gets too large the kernel may decide to swap out portions of
> it that haven't been touched lately. This of course is completely
> counterproductive, especially if what gets swapped is a dirty buffer,
> which'll eventually have to be read back in and then written to where
> it should have gone. This is the main factor behind my thought that you
> don't want to skimp on kernel disk buffer space --- any memory pressure
> in the system should be resolvable by dropping kernel disk buffers, not
> by starting to swap shmem or user processes.
>
You can lock shared memory for this problem ?
regards
haris peco
