From owner-freebsd-current Tue Feb 29 10:47:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id F208737BC6C for ; Tue, 29 Feb 2000 10:47:36 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA85965; Tue, 29 Feb 2000 10:47:33 -0800 (PST) (envelope-from dillon) Date: Tue, 29 Feb 2000 10:47:33 -0800 (PST) From: Matthew Dillon Message-Id: <200002291847.KAA85965@apollo.backplane.com> To: Christopher Masto Cc: Cliff Rowley , Alfred Perlstein , freebsd-current@FreeBSD.ORG Subject: Re: Shared memory - Was: 2 Queries References: <20000229021327.E21720@fw.wintelcom.net> <20000229134143.B4903@netmonger.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> are almost identical in nature to the ones I've been getting from other :> programs *not* gtk/gdk based ;) The link between them so far is shared :> memory... : :Personally, I have this extreme distaste for sysv shared memory. It :is a very scarce resource that is not freed automatically, and seems :to go completely against the unix model. Reminds me of having to free :memory on the Amiga, and slowly running out of chip RAM. : :In any case, one major offender is imlib. Since I've recently gone :Gnome, I've had to turn off imlib's "MIT-SHM shared memory" option :or things would go bad after a few minutes or hours of use. :-- :Christopher Masto Senior Network Monkey NetMonger Communications :chris@netmonger.net info@netmonger.net http://www.netmonger.net : :Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ Maybe we can convince them / submit patches to use mmap() based shared memory (file-backed), which we can now do efficiently with the MAP_NOSYNC option. I have a love-hate relationship with SysV shared memory. On the one hand it is virtually guarenteed to work across all UNIX platforms. On the otherhand most platforms have absurd resource limitations applied to SysV shared memory calls. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message