From owner-freebsd-hackers Fri Dec 1 22:43:32 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA26469 for hackers-outgoing; Fri, 1 Dec 1995 22:43:32 -0800 Received: from pinch.io.org (root@pinch.io.org [198.133.36.9]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA26459 for ; Fri, 1 Dec 1995 22:43:17 -0800 Received: from flinch (flinch.io.org [198.133.36.153]) by pinch.io.org (8.6.9/8.6.9) with SMTP id BAA04260; Sat, 2 Dec 1995 01:41:23 -0500 Date: Sat, 2 Dec 1995 01:40:55 -0500 (EST) From: Brian Tao X-Sender: taob@flinch To: Terry Lambert cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Increasing size of shared memory segmenty In-Reply-To: <199511292110.OAA28629@phaeton.artisoft.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@FreeBSD.ORG Precedence: bulk On Wed, 29 Nov 1995, Terry Lambert wrote: > > 32M is smaller than the overall limit, (36 bits? 39 bits?) so you should > be safe, though if you have several of these, you will probably start > having problems. Okay... I gather I need to bump up SHMMAX (max. segment size) as well as SHMALL (max. total size of all segments?). I'm running a 2.1.0-RELEASE kernel with these settings: shminfo: shmmax: 16777216 (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: 4096 (max amount of shared memory in pages) Seems to be working okay so far, although I still can't load those nice 1536x1024 (or larger) PhotoCD pictures into gimp... :( -- Brian Tao (BT300, taob@io.org) Systems Administrator, Internex Online Inc. "Though this be madness, yet there is method in't"