From: Christopher Quinn <cq@htec.demon.co.uk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Interprocess shared memory .... but file backed?
Date: Fri, 08 Mar 2002 15:30:56 +0000 [thread overview]
Message-ID: <3C88D930.2080308@htec.demon.co.uk> (raw)
In-Reply-To: <E16jMMJ-0006V3-00@the-village.bc.nu>
Alan Cox wrote:
>>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
>>
>
> well MAP_PRIVATE is "dont share" so not with that 8)
> Use MAP_SHARED and you'll get what you want
>
>
Certainly true! But MAP_SHARED gives uncontrolled flush of
dirty data - so that's out for me. I only want 'privacy' to
extend to the right to make changes permanent at my own
discretion.
Chris Q.
--
rgrds,
Chris Quinn
next prev parent reply other threads:[~2002-03-08 15:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-08 15:08 Interprocess shared memory .... but file backed? Christopher Quinn
2002-03-08 15:32 ` Alan Cox
2002-03-08 15:30 ` Christopher Quinn [this message]
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=3C88D930.2080308@htec.demon.co.uk \
--to=cq@htec.demon.co.uk \
--cc=alan@lxorguk.ukuu.org.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