From owner-freebsd-hackers  Sun Jul  7 10:06:38 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id KAA21665
          for hackers-outgoing; Sun, 7 Jul 1996 10:06:38 -0700 (PDT)
Received: from terra.Sarnoff.COM (terra.sarnoff.com [130.33.11.203])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id KAA21652
          for <hackers@FreeBSD.ORG>; Sun, 7 Jul 1996 10:06:34 -0700 (PDT)
Received: (from rminnich@localhost) by terra.Sarnoff.COM (8.6.12/8.6.12) id NAA14680; Sun, 7 Jul 1996 13:05:26 -0400
Date: Sun, 7 Jul 1996 13:05:26 -0400 (EDT)
From: "Ron G. Minnich" <rminnich@Sarnoff.COM>
X-Sender: rminnich@terra
To: Tom Bartol <bartol@salk.edu>
cc: hackers@FreeBSD.ORG
Subject: Re: Shared Memory Questions
In-Reply-To: <Pine.SUN.3.93.960705234755.17590A-100000@helmholtz>
Message-ID: <Pine.SUN.3.91.960707130306.14662B-100000@terra>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


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' :=)

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. 

ron