From owner-freebsd-hackers Mon Dec 9 18:39:22 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA27483 for hackers-outgoing; Mon, 9 Dec 1996 18:39:22 -0800 (PST) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA27470 for ; Mon, 9 Dec 1996 18:39:17 -0800 (PST) Received: (from root@localhost) by dyson.iquest.net (8.8.2/8.6.9) id VAA27569; Mon, 9 Dec 1996 21:38:50 -0500 (EST) From: "John S. Dyson" Message-Id: <199612100238.VAA27569@dyson.iquest.net> Subject: Re: Multiple Buffer allocation of Shared Memory To: erich@lodgenet.com (Eric L. Hernes) Date: Mon, 9 Dec 1996 21:38:50 -0500 (EST) Cc: scrappy@hub.org, hackers@FreeBSD.ORG In-Reply-To: <199612100156.TAA00658@jake.lodgenet.com> from "Eric L. Hernes" at Dec 9, 96 07:56:17 pm Reply-To: dyson@FreeBSD.ORG X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Shared memory is cool, SysV symantics for shared memory *suck*, if at all > possible use mmap(). BSDi uses libc wrappers around mmap() for > it's SysV shm stuff, but there's caveats... I'd like the wrappers, > but have the real ones available too. > FreeBSD, NetBSD, and OpenBSD have a low level implementation of the SYSVSHM stuff (not based on mmap, but on some of the low level kernel primatives that are also used to implement mmap.) > > you can only have 8 shm segments by default, you can override > it with: `options "SHMSEG=32"' or something similar in your config file. > I usually bump SHMSEG to 128 and SHMMAXPGS to 4096. > The limits on FreeBSD are totally administrative, and so if you need to increase SHMMAXPGS or somesuch, there is little cost. John dyson@freebsd.org