Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 11 Jan 2003 16:53:11 -0800 (PST)
From:      Matthew Dillon <dillon@apollo.backplane.com>
To:        "Alan L. Cox" <alc@imimic.com>
Cc:        Peter Wemm <peter@wemm.org>, arch@FreeBSD.ORG
Subject:   Re: Virtual memory question
Message-ID:  <200301120053.h0C0rBR1072243@apollo.backplane.com>
References:  <20030111224444.94D102A89E@canning.wemm.org> <200301112342.h0BNgj9a048596@apollo.backplane.com> <3E20B747.1FCA3B36@imimic.com>

next in thread | previous in thread | raw e-mail | index | archive | help

:
:Matthew Dillon wrote:
:> ...
:>     How about something like:
:> 
:>         getmemfd().
:> 
:
:Roughly speaking, this is shm_open(3), which we currently implement
:using files.
:
:Alan

   Except without the path rendezvous (which in sysv land may not even
   represent a real filesystem path).  I do not think we would want to
   make this compatible with the brokekn SysV SHM API.  It's just too
   broken.

   Interesting.  This brings to mind the 'fifo' filesystem 
   object type.  You know, ala 'mkfifo'.  There might be an advantage
   to that, then a normal open() could be used to get the shared
   memory object.

	mkshmem	- make a shared memory object that can be open()'d.
		  (ala mkfifo).

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200301120053.h0C0rBR1072243>