From: Jamie Lokier <lk@tantalophile.demon.co.uk>
To: "Stephen C. Tweedie" <sct@redhat.com>
Cc: Christoph Rohland <cr@sap.com>,
Rik van Riel <riel@conectiva.com.br>,
linux-mm@kvack.org
Subject: Re: [PATCH] VM kswapd autotuning vs. -ac7
Date: Wed, 7 Jun 2000 16:09:31 +0200 [thread overview]
Message-ID: <20000607160931.C22749@pcep-jamie.cern.ch> (raw)
In-Reply-To: <20000607143242.D30951@redhat.com>; from sct@redhat.com on Wed, Jun 07, 2000 at 02:32:42PM +0100
Stephen C. Tweedie wrote:
> The main reason SHM needs its own swap code is that normal anonymous
> pages are referred to only from ptes --- the ptes either point to
> the physical page containing the page, or to the swap entry. We
> cannot use that for SHM, because SysV SHM segments must be persistent
> even if there are no attachers, and hence no ptes to maintain the
> location of the pages.
It might be possible to create MMs without tasks specifically to map the
SHM segments.
-- Jamie
--
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-06-07 14:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-01 22:31 Rik van Riel
2000-06-02 15:54 ` Christoph Rohland
2000-06-02 16:01 ` Rik van Riel
2000-06-03 9:02 ` Christoph Rohland
2000-06-03 20:47 ` Rik van Riel
2000-06-04 11:12 ` Christoph Rohland
2000-06-05 8:58 ` Christoph Rohland
2000-06-05 10:16 ` Rik van Riel
2000-06-07 10:23 ` Christoph Rohland
2000-06-07 12:43 ` Rik van Riel
2000-06-07 13:04 ` Christoph Rohland
2000-06-07 13:39 ` Rik van Riel
2000-06-07 14:29 ` Christoph Rohland
2000-06-07 14:43 ` Stephen C. Tweedie
2000-06-08 15:04 ` [PATCH,incomplete] shm integration into shrink_mmap Christoph Rohland
2000-06-08 15:21 ` Juan J. Quintela
2000-06-08 15:35 ` Rik van Riel
2000-06-07 13:32 ` [PATCH] VM kswapd autotuning vs. -ac7 Stephen C. Tweedie
2000-06-07 14:09 ` Jamie Lokier [this message]
2000-06-07 14:11 ` Christoph Rohland
2000-06-07 14:17 ` Stephen C. Tweedie
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=20000607160931.C22749@pcep-jamie.cern.ch \
--to=lk@tantalophile.demon.co.uk \
--cc=cr@sap.com \
--cc=linux-mm@kvack.org \
--cc=riel@conectiva.com.br \
--cc=sct@redhat.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