From owner-freebsd-hackers  Mon Jul  8 13:55:32 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id NAA07922
          for hackers-outgoing; Mon, 8 Jul 1996 13:55:32 -0700 (PDT)
Received: from tombstone.sunrem.com (tombstone.sunrem.com [206.81.134.54])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id NAA07916
          for <hackers@freebsd.org>; Mon, 8 Jul 1996 13:55:28 -0700 (PDT)
Received: (from brandon@localhost) by tombstone.sunrem.com (8.6.12/8.6.12) id OAA02225; Mon, 8 Jul 1996 14:55:00 -0600
Date: Mon, 8 Jul 1996 14:55:00 -0600 (MDT)
From: Brandon Gillespie <brandon@tombstone.sunrem.com>
To: "Ron G. Minnich" <rminnich@Sarnoff.COM>
cc: Tom Bartol <bartol@salk.edu>, hackers@freebsd.org
Subject: Re: Shared Memory Questions
In-Reply-To: <Pine.SUN.3.91.960707130306.14662B-100000@terra>
Message-ID: <Pine.BSF.3.91.960708145432.2220A-100000@tombstone.sunrem.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

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' :=)
> 
> 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 have a friend who would love to take a look at your source, pointers?

-Brandon Gillespie