From owner-freebsd-questions Mon Jul 8 02:54:25 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id CAA21514 for questions-outgoing; Mon, 8 Jul 1996 02:54:25 -0700 (PDT) Received: from sam.networx.ie (dublin-ts4-101.indigo.ie [194.125.133.101]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id CAA21505 for ; Mon, 8 Jul 1996 02:54:16 -0700 (PDT) Received: from mip1.networx.ie (mip1.networx.ie [194.9.12.1]) by sam.networx.ie (8.6.12/8.6.12) with SMTP id IAA12368; Mon, 8 Jul 1996 08:53:50 GMT X-Organisation: I.T. NetworX Ltd X-Business: Network Consultancy and Training X-Address: 67 Merrion Square, Dublin 2, Ireland X-Voice: +353-1-676-8866 X-Fax: +353-1-676-8868 Received: from mike.networx.ie by mip1.networx.ie Date: Mon, 8 Jul 1996 08:52:24 BST From: Michael Ryan Reply-To: mike@NetworX.ie Subject: Re: Shared Memory Questions To: Tom Bartol Cc: FreeBSD Support Message-Id: Priority: Normal Mime-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Tom, I dunno if the following is any use to you, but I wrote an application that uses shared memory (it has small shm requirements) and here's what I set my kernconfig file to. I also had to make a slight mod to ipcs.c, to stop it from aborting on seg violations. It was a small mod -- the code was referencing an incorrect variable (as a result of the programmer cutting and pasting?). I don't have the source code to hand. If you like, I'll dig it out and post the changes to you. ------------------------------------------------------------ # # These three options provide support for System V Interface # Definition-style interprocess communication, in the form of shared # memory, semaphores, and message queues, respectively. # #options SYSVSHM #options SYSVSEM #options SYSVMSG # # mjmr 951126 Tune sems and shms. # #options "SHMMAXPGS=128" # 512KB shm #options "SHMMAX=16384" #options "SHMMIN=1" #options "SHMMNI=256" #options "SHMSEG=128" #options "SHMALL=300" #options "SEMMNI=256" #options "SEMMAP=30" #options "SEMMNS=500" #options "SEMMNU=30" # MR951127 The option SEMMSL restricts the number of semaphores that can # be *deleted*, but not the number that can be created. From various # descriptions, it would appear it should do neither. For a good margin, # I've given it the same value as SEMMNI. #options "SEMMSL=256" #options "SEMOPM=10" #options "SEMUME=10" #options "SEMVMX=32768" # hardwired in /usr/src/sys/sys/sem.h #options "SEMAEM=16384" # so we won't redefine here ------------------------------------------------------------ Mike ---