Date: Wed, 10 Feb 1999 18:27:03 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: dg@root.com Cc: tlambert@primenet.com, dillon@apollo.backplane.com, kuku@gilberto.physik.RWTH-Aachen.DE, hackers@FreeBSD.ORG Subject: Re: portability of shm, mmap, pipes and socket IPC Message-ID: <199902101827.LAA17659@usr07.primenet.com> In-Reply-To: <199902101742.JAA17281@implode.root.com> from "David Greenman" at Feb 10, 99 09:42:16 am
next in thread | previous in thread | raw e-mail | index | archive | help
> >> >: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. Gotcha. I didn't read it in much depth; I'd assumed that "_s" was "segment", not "state". I thought the "handle" malloc was the state. Mea culpa. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199902101827.LAA17659>