From: "Stephen C. Tweedie" <sct@redhat.com>
To: Christoph Rohland <hans-christoph.rohland@sap.com>
Cc: fxzhang@chpc.ict.ac.cn, "linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: Why don't we make mmap MAP_SHARED with /dev/zero possible?
Date: Tue, 26 Oct 1999 13:05:02 +0100 (BST) [thread overview]
Message-ID: <14357.39150.714844.910876@dukat.scot.redhat.com> (raw)
In-Reply-To: <qwwg0yymv5a.fsf@sap.com>
Hi,
On 26 Oct 1999 09:35:45 +0200, Christoph Rohland
<hans-christoph.rohland@sap.com> said:
> Yes I would like to see it also, but at least in 2.0 days it was
> really difficult/impossible.
In 2.2 it is much easier --- I did most of the required work when
making swap cache sharing persistant. Then the 2.2 codefreeze hit...
The first remaining problem is initialisation of demand-zero pages for
shared vmas. You have to be able to ensure that when one process
faults in a shared page for the first time, all other processes pick
up the correct new page.
There are several ways you could do this. The SysV-shm mechanism
would work, but it would be harder to garbage-collect all of the
resources used by a page which is no longer shared. Normal
demand-zero page instantiation would work provided that it was
performed atomically over all the vmas concerned, which would require
careful locking on 2.3 for SMP.
The only fly in the ointment is that 2.3's new bigmem code doesn't
observe the swap cache rules so carefully, and shared pages can become
separated. We'd have to make the swap cache capable of working
properly on high memory pages.
The other thing still needing done is to make the swap cache work
properly for writable pages --- there are still various places in the
VM where we assume mapped swap cache pages are readonly.
--Stephen
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
next prev parent reply other threads:[~1999-10-26 12:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-26 1:57 fxzhang
1999-10-26 7:35 ` Christoph Rohland
1999-10-26 12:05 ` Stephen C. Tweedie [this message]
1999-10-26 12:07 ` Stephen C. Tweedie
[not found] <qwwzox6l3nh.fsf@sap.com>
1999-11-03 14:29 ` Ingo Molnar
1999-11-03 14:50 ` Eric W. Biederman
1999-11-03 16:46 ` Ingo Molnar
1999-11-03 18:55 ` Eric W. Biederman
1999-11-03 19:16 ` Eric W. Biederman
1999-11-03 20:24 ` Ingo Molnar
1999-11-03 19:32 ` Benjamin C.R. LaHaise
1999-11-03 21:41 ` Ingo Molnar
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=14357.39150.714844.910876@dukat.scot.redhat.com \
--to=sct@redhat.com \
--cc=fxzhang@chpc.ict.ac.cn \
--cc=hans-christoph.rohland@sap.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