From: "Stephen C. Tweedie" <sct@redhat.com>
To: Hugh Dickins <hugh@veritas.com>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
Andrea Arcangeli <andrea@suse.de>, Ben LaHaise <bcrl@redhat.com>,
Marcelo Tosatti <marcelo@conectiva.com.br>,
Rik van Riel <riel@conectiva.com.br>,
linux-mm@kvack.org
Subject: Re: SWAP_MAP_MAX: How?
Date: Fri, 24 Aug 2001 14:07:49 +0100 [thread overview]
Message-ID: <20010824140749.C4389@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0108241323280.1044-100000@localhost.localdomain>; from hugh@veritas.com on Fri, Aug 24, 2001 at 01:42:59PM +0100
Hi,
On Fri, Aug 24, 2001 at 01:42:59PM +0100, Hugh Dickins wrote:
> Doesn't it need an anonymous page mapped multiple (e.g. 256) times
> into multiple (e.g. 256) mms to reach the limit?
That would do it, yes.
> And there's an obvious
> way that can happen, by multiply attaching a piece of IPC Shared Memory,
> and multiply forking. But in that case it's the shared memory object
> which gets the large number of references, and the swap counts stay 1.
Indeed --- sysV shm swapping is eccentric. :-)
There _was_ once a way to do this --- mmap()ing another process's
/proc/*/mem would allow you to get a swap page mapped into memory
multiple times, but we removed support for that way back in pre-2.2
days. I don't think we allow that any more, unless it's been
reenabled again.
Cheers,
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://www.linux-mm.org/
next prev parent reply other threads:[~2001-08-24 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-24 11:16 Hugh Dickins
2001-08-24 11:19 ` Stephen C. Tweedie
2001-08-24 12:42 ` Hugh Dickins
2001-08-24 13:07 ` Stephen C. Tweedie [this message]
2001-08-25 10:35 ` Hugh Dickins
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=20010824140749.C4389@redhat.com \
--to=sct@redhat.com \
--cc=andrea@suse.de \
--cc=bcrl@redhat.com \
--cc=hugh@veritas.com \
--cc=linux-mm@kvack.org \
--cc=marcelo@conectiva.com.br \
--cc=riel@conectiva.com.br \
/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