Date: Sat, 11 Jan 2003 17:09:33 -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: <200301120109.h0C19Xch000211@apollo.backplane.com> References: <20030111224444.94D102A89E@canning.wemm.org> <200301112342.h0BNgj9a048596@apollo.backplane.com> <3E20B747.1FCA3B36@imimic.com> <200301120053.h0C0rBR1072243@apollo.backplane.com> <3E20BEE8.61F8D9CD@imimic.com>
next in thread | previous in thread | raw e-mail | index | archive | help
:
:Matthew Dillon wrote:
:> ...
:> 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.
:
:shm_open(3) is for use with mmap(2). It really has nothing to do with
:System V SHM.
:
:Alan
I meant this comment in the manual page:
"The path argument does not necessarily represent a pathname (although it
does in this and most other implementations). Two processes opening the
same path are guaranteed to access the same shared memory object if and
only if path begins with a slash (`/') character."
Which implies that the code must support non-path string identifiers
to be POSIX compliant. I should have said POSIX breakage instead of
SysV breakage I suppose.
-Matt
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?200301120109.h0C19Xch000211>