From: Christoph Rohland <hans-christoph.rohland@sap.com>
To: Kanoj Sarcar <kanoj@google.engr.sgi.com>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
Linus Torvalds <torvalds@transmeta.com>,
linux-mm@kvack.org, Ingo Molnar <mingo@chiara.csoma.elte.hu>
Subject: Re: [RFC] [RFT] Shared /dev/zero mmaping feature
Date: 08 Mar 2000 13:02:51 +0100 [thread overview]
Message-ID: <qww7lfdr7o4.fsf@sap.com> (raw)
In-Reply-To: kanoj@google.engr.sgi.com's message of "Mon, 6 Mar 2000 15:01:43 -0800 (PST)"
Hi Kanoj,
kanoj@google.engr.sgi.com (Kanoj Sarcar) writes:
> > To make this work for shared anonymous pages, we need two changes
> > to the swap cache. We need to teach the swap cache about writable
> > anonymous pages, and we need to be able to defer the physical
> > writing of the page to swap until the last reference to the swap
> > cache frees up the page. Do that, and shared /dev/zero maps will
> > Just Work.
>
> The current implementation of /dev/zero shared memory is to treat
> the mapping as similarly as possible to a shared memory segment. The
> common code handles the swap cache interactions, and both cases
> qualify as shared anonymous mappings. While its not well tested, in
> theory it should work. We are currently agonizing over how to
> integrate the /dev/zero code with shmfs patch.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Since this is not as easy as you thought, wouldn't it be better to do
the /dev/zero shared maps in the swap cache instead of this workaround
over shm? Thus we would get the mechanisms to redo all shm stuff wrt
swap cache.
At the same time we would not hinder the development of normal shm
code to use file semantics (aka shm fs) which will give us posix shm.
Greetings
Christoph
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux.eu.org/Linux-MM/
next prev parent reply other threads:[~2000-03-08 12:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-25 23:08 Kanoj Sarcar
2000-02-26 16:38 ` Linus Torvalds
2000-02-26 21:47 ` Kanoj Sarcar
2000-02-29 10:54 ` Christoph Rohland
2000-02-29 18:30 ` Kanoj Sarcar
2000-03-01 12:08 ` Christoph Rohland
2000-03-01 17:34 ` Kanoj Sarcar
2000-03-01 17:55 ` Christoph Rohland
2000-03-01 18:18 ` Kanoj Sarcar
2000-03-01 19:42 ` Christoph Rohland
2000-03-01 20:09 ` Kanoj Sarcar
2000-03-06 22:43 ` Stephen C. Tweedie
2000-03-06 23:01 ` Kanoj Sarcar
2000-03-08 12:02 ` Christoph Rohland [this message]
2000-03-08 17:51 ` Kanoj Sarcar
2000-03-08 18:35 ` Christoph Rohland
2000-03-08 18:48 ` Linus Torvalds
2000-03-08 18:57 ` Kanoj Sarcar
2000-03-09 18:15 ` Christoph Rohland
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=qww7lfdr7o4.fsf@sap.com \
--to=hans-christoph.rohland@sap.com \
--cc=kanoj@google.engr.sgi.com \
--cc=linux-mm@kvack.org \
--cc=mingo@chiara.csoma.elte.hu \
--cc=sct@redhat.com \
--cc=torvalds@transmeta.com \
/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