From owner-freebsd-hackers Wed Feb 10 09:53:47 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA27015 for freebsd-hackers-outgoing; Wed, 10 Feb 1999 09:53:47 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from implode.root.com (root.com [208.221.12.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA27010 for ; Wed, 10 Feb 1999 09:53:45 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id JAA17281; Wed, 10 Feb 1999 09:42:16 -0800 (PST) Message-Id: <199902101742.JAA17281@implode.root.com> To: Terry Lambert cc: dillon@apollo.backplane.com, kuku@gilberto.physik.RWTH-Aachen.DE, hackers@FreeBSD.ORG Subject: Re: portability of shm, mmap, pipes and socket IPC In-reply-to: Your message of "Wed, 10 Feb 1999 17:24:00 GMT." <199902101724.KAA13526@usr07.primenet.com> From: David Greenman Reply-To: dg@root.com Date: Wed, 10 Feb 1999 09:42:16 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >:The overall size of the shared memory segment is limited to that >> >: which can fit in the kernels virtual address space; this >> >: artificially restricts the maximum size. >> >> That isn't true and hasn't been true for several years in FreeBSD. > >Are you sure? Yes, I'm quite sure. >>From my reading of sysv_shm.c: > > shmmap_s = malloc(size, M_SHM, M_WAITOK); > >seems to limit the size to what's allocable in the KVA. The above malloc allocates space for a struct shmmap_state. RTSL. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message