From owner-freebsd-questions Tue Nov 7 10:49:02 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id KAA29238 for questions-outgoing; Tue, 7 Nov 1995 10:49:02 -0800 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id KAA29228 for ; Tue, 7 Nov 1995 10:48:41 -0800 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id LAA18058; Tue, 7 Nov 1995 11:44:45 -0700 From: Terry Lambert Message-Id: <199511071844.LAA18058@phaeton.artisoft.com> Subject: Re: kernel MIT-SHM extensions ?? To: pecold@abrcp.cz Date: Tue, 7 Nov 1995 11:44:45 -0700 (MST) Cc: freebsd-questions@freebsd.org In-Reply-To: <199511071456.PAA23692@abrcp.abrcp.cz> from "Petr Kodl" at Nov 7, 95 03:56:10 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1198 Sender: owner-questions@freebsd.org Precedence: bulk > What's the MIT-SHM kernel extension ?? It's an extension to the X transport mechanism so that locally running apps with Xlib can directly access memory instead of having to use the standard (slower) IPC mechanisms of net or POSIX domain sockets. > Is it supported by 2.0.5 release kernel ?? I believe you would need to rebuild a release kernel to add: # # 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 To your kernel configuration file to get shared memory support with 2.0.5. Other than the underlying transport, it's entirely up to the X client and server if the extension is supported. > If it is, how can I add it to the kernel configuration file ?? See above. > The X-server option does not change the behavior in this point, so > what is it exactly this option for ?? Fast animation, mostly. Like the X version of DOOM or ASCENT. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.