Date: Sun, 7 Jul 1996 15:06:02 -0400 (EDT) From: "Marc G. Fournier" <scrappy@ki.net> To: "Ron G. Minnich" <rminnich@Sarnoff.COM> Cc: Tom Bartol <bartol@salk.edu>, hackers@freebsd.org Subject: Re: Shared Memory Questions Message-ID: <Pine.NEB.3.94.960707150313.12204B-100000@ki.net> In-Reply-To: <Pine.SUN.3.91.960707130306.14662B-100000@terra>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 7 Jul 1996, Ron G. Minnich wrote:
>
> actually, you're not really running out of shared memory. You're running
> out of sysv shared memory, which is barely a qualifier for the name
> 'shared memory' :=)
>
Okay...can I increase that? :)
ipcs -M shows:
postgres@zeus> ipcs -M
shminfo:
shmmax: 4194304 (max shared memory segment size)
shmmin: 1 (min shared memory segment size)
shmmni: 32 (max number of shared memory identifiers)
shmseg: 8 (max shared memory segments per process)
shmall: 1024 (max amount of shared memory in pages)
So would have assumed I had 4Meg of Shared Memory available, no?
> Does the tool you're using use the shared memory just as shared memory,
> and not for locks, etc.? If so, you're better off setting up shared
> mmap'ed files, since there will be no limit. I have a simple allocater
> called filemalloc and filecalloc that does this, if you want them let me
> know. Works much better than sysv shm.
>
I haven't got a clue...I'm running Postgres95, which uses SYSV shared
memory...anyone out there know the answer to this one? :)
Marc G. Fournier scrappy@ki.net
Systems Administrator @ ki.net scrappy@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.94.960707150313.12204B-100000>