From: James Bottomley <James.Bottomley@steeleye.com>
To: Daniel Phillips <phillips@arcor.de>
Cc: Jamie Lokier <jamie@shareable.org>,
Linus Torvalds <torvalds@osdl.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fix remap of shared read only mappings
Date: 04 Sep 2003 20:52:36 -0400 [thread overview]
Message-ID: <1062723158.1829.541.camel@mulgrave> (raw)
In-Reply-To: <200309050249.21152.phillips@arcor.de>
On Thu, 2003-09-04 at 20:49, Daniel Phillips wrote:
> This an interesting tidbit, as I'm busy working on a DFS mmap for OpenGFS, and
> I want to be sure I'm implementing true-blue Posix semantics. But trawling
> through the Posix/SUS specification at:
>
> http://www.unix-systems.org/version3/online.html
>
> all it says is that for MAP_SHARED "write references shall change the
> underlying object." I don't see anything about when those changes become
> visible to other mappers, much less any discussion of local caching. Am I
> looking at the wrong document?
Not sure which is "correct", but the one I'm looking at is the POSIX
update from the open group:
http://www.opengroup.org/onlinepubs/007904975/functions/mmap.html
And that's where I was quoting from.
James
next prev parent reply other threads:[~2003-09-05 0:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 14:49 [PATCH] fix remap of shared read only mappings James Bottomley
2003-09-04 21:48 ` Jamie Lokier
2003-09-04 22:33 ` James Bottomley
2003-09-04 22:56 ` Jamie Lokier
2003-09-04 23:23 ` James Bottomley
2003-09-04 23:40 ` Jamie Lokier
2003-09-05 0:49 ` Daniel Phillips
2003-09-05 0:49 ` Linus Torvalds
2003-09-05 1:07 ` Alan Cox
2003-09-05 1:31 ` Daniel Phillips
2003-09-05 4:35 ` Linus Torvalds
2003-09-05 0:52 ` James Bottomley [this message]
2003-09-05 1:21 ` Daniel Phillips
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1062723158.1829.541.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@arcor.de \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.