From: Jan Dvorak <mordae@anilinux.org>
To: Christoph Lameter <cl@linux.com>
Cc: linux-mm@kvack.org
Subject: Re: COW userspace memory mapping question
Date: Fri, 11 Mar 2011 17:33:13 +0100 [thread overview]
Message-ID: <20110311173313.f427fb3b.mordae@anilinux.org> (raw)
In-Reply-To: <alpine.DEB.2.00.1103110914290.18585@router.home>
[-- Attachment #1: Type: text/plain, Size: 501 bytes --]
On Fri, 11 Mar 2011 09:15:42 -0600 (CST), Christoph Lameter <cl@linux.com> wrote:
> Keep the RW mapping around and tear down and repeat the MAP_PRIVATE mmaps
> areas as needed? Updates would have to be done to the RW mapping.
Hmm, I can create a shared mapping and snapshot normally using the private
mapping. Only thing I need to do in order to ensure I will still see the
original state in the private map is to write something to it before every
update of the shared map. Is that correct?
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2011-03-11 16:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 21:38 COW userspace memory mapping question Mordae
2011-03-10 19:13 ` Christoph Lameter
2011-03-10 21:00 ` Mordae
2011-03-10 21:33 ` Christoph Lameter
2011-03-10 22:11 ` Mordae
2011-03-11 15:15 ` Christoph Lameter
2011-03-11 16:33 ` Jan Dvorak [this message]
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=20110311173313.f427fb3b.mordae@anilinux.org \
--to=mordae@anilinux.org \
--cc=cl@linux.com \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).