>>>>> On Fri, 5 Jul 2002 16:28:24 +0900 (JST),
	Curt Sampson <cjs@cynic.net> said:

> 5. Some programs, it appears to me, don't expected shared memory to be
> pagable. A particular example would be database programs, which use
> shared memory for buffering blocks from disk. Needless to say, the naive
> user who cranks up his shared memory segments to be most of system RAM
> in the hope of improving his Oracle buffering performance is in for a
> bit of a surprise!

How about adding following operations to shmctl(2)?

  From shmctl(2) man page of SunOS5.8:

     SHM_LOCK
           Lock the shared memory segment specified by  shmid  in
           memory. This command can be executed only by a process
           that has an effective user ID equal to super-user.

     SHM_UNLOCK
           Unlock the shared memory segment specified  by  shmid.
           This  command  can  be executed only by a process that
           has an effective user ID equal to super-user.
--
soda