From: Christopher Quinn <cq@htec.demon.co.uk>
To: linux-kernel@vger.kernel.org
Cc: Christopher Quinn <cq@htec.demon.co.uk>
Subject: Interprocess shared memory .... but file backed?
Date: Fri, 08 Mar 2002 15:08:34 +0000 [thread overview]
Message-ID: <3C88D3F2.40807@htec.demon.co.uk> (raw)
Hello,
I know that a combination of mmap/shmem can be used to
achieve interprocess shared memory (notably Ralf
Engelschall's MM library).
However as far as I can tell this is anonymous memory only.
Are there any options if one initially maps a disk file via
mmap (in particular MAP_PRIVATE) for sharing that vm, such
that any access by a member of the sharing process group
will fault in the relevant file data page after which writes
to it are seen by all?
Of course clone(2) will give the necessary sharing of page
tables but my ideal is for sharing only of specified areas
of vm, not everything.
Anyone know of a way of doing this?
Thanks,
Chris Quinn
PS. I'm not subscribed! please ensure you CC. me!!
next reply other threads:[~2002-03-08 15:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-08 15:08 Christopher Quinn [this message]
2002-03-08 15:32 ` Interprocess shared memory .... but file backed? Alan Cox
2002-03-08 15:30 ` Christopher Quinn
2002-03-08 19:20 ` H. Peter Anvin
2002-03-08 15:51 ` Richard B. Johnson
[not found] <Pine.LNX.4.33.0203081049360.15002-100000@coffee.psychology.mcmaster.ca>
2002-03-08 16:05 ` Christopher Quinn
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=3C88D3F2.40807@htec.demon.co.uk \
--to=cq@htec.demon.co.uk \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox