From owner-freebsd-questions Fri Sep 6 20:28:26 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id UAA26757 for questions-outgoing; Fri, 6 Sep 1996 20:28:26 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id UAA26741 for ; Fri, 6 Sep 1996 20:28:19 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id WAA00240; Fri, 6 Sep 1996 22:27:58 -0500 (EST) From: "John S. Dyson" Message-Id: <199609070327.WAA00240@dyson.iquest.net> Subject: Re: SYSV Shared Memory Question To: rwm@MPGN.COM (Rob Miracle) Date: Fri, 6 Sep 1996 22:27:58 -0500 (EST) Cc: freebsd-questions@FreeBSD.ORG In-Reply-To: <3.0b11.32.19960906110535.00727e2c@central.TanSoft.COM> from "Rob Miracle" at Sep 6, 96 11:05:37 am 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-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > We need a boat load of SYSV shared memory and we get a Kernel panic when we > try to request it. Here are the specifics: > > PentiumPro 200, 256M memory > We need 22000 pages of Shared memory for one application, and a little bit > more. On Ultrix 4.4, we declare smmax at 24000 and smseg 32 and things work > well. The total shared memory can be any amount. > > On our FreeBSD 2.x.x (we have tried 2.1.0, 2.1.5, and 2.2.snap (most recent)) > when we set SHMMAXPGS to 22000 and SHMALL to something over 30000, we get a > kernel panic in kmem_suballoc of type 3. > I think that I have corrected the code in 2.2-current. You can just grab the new sysv_shm in current, and it will probably work in 2.2-snap. The SHM segments no longer take any significant KVA space. The code might be buggy, but the changes are pretty simple, and I have tested the operation of the SHM by using xanim with the SVSHM option (+B) and it appears to work. Good Luck!!! John