From: kanoj@google.engr.sgi.com (Kanoj Sarcar)
To: Ingo Molnar <mingo@chiara.csoma.elte.hu>
Cc: riel@nl.linux.org, jgarzik@mandrakesoft.com,
alan@lxorguk.ukuu.org.uk, linux-kernel@vger.rutgers.edu,
linux-mm@kvack.org
Subject: Re: Getting big areas of memory, in 2.3.x?
Date: Thu, 9 Dec 1999 14:27:26 -0800 (PST) [thread overview]
Message-ID: <199912092227.OAA10455@google.engr.sgi.com> (raw)
In-Reply-To: <Pine.LNX.4.10.9912100018160.11167-100000@chiara.csoma.elte.hu> from "Ingo Molnar" at Dec 10, 99 00:21:18 am
>
>
> On Thu, 9 Dec 1999, Kanoj Sarcar wrote:
>
> > Well, at least in 2.3, kernel data (and page caches) are below 1G,
> > which means there's a lot of memory possible out there with
> > references only from user memory. Shm page references are
> > revokable too. [...]
>
> we already kindof replace pages, see replace_with_highmem(). Reverse ptes
> do help, but are not a necessity to get this. Neither reverse ptes, nor
> any other method guarantees that a large amount of continuous RAM can be
> allocated. Only boot-time allocation can be guaranteed.
>
> -- mingo
>
Unfortunately, a bunch of these drivers are loadable modules, so unless
they do some trickery, boot-time allocation does not apply for them.
A similar category of drivers would like to do this dynamically too.
For drivers that want to do this a fixed number of time at bootup,
yes, boot-time allocation is the answer ...
If I am not wrong, replace_with_highmem() replaces a page when the
kernel is quite sure there's exactly one reference on the page, and
that is from the executing code. For the dynamic case, the problem
is in trying to rip away unknown number of kernel/user references
from a given page. Rmaps do not guarantee it, they just improve the
chances of success in such problems at an affordable cost.
Kanoj
--
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-12-09 22:27 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-12-09 1:03 Jeff Garzik
1999-12-09 2:28 ` Alan Cox
1999-12-09 2:45 ` Jeff Garzik
1999-12-09 5:22 ` Oliver Xymoron
1999-12-09 12:25 ` Ingo Molnar
1999-12-09 20:24 ` Jeff Garzik
1999-12-09 20:31 ` Kanoj Sarcar
1999-12-09 20:39 ` Rik van Riel
1999-12-09 20:54 ` Kanoj Sarcar
1999-12-09 23:21 ` Ingo Molnar
1999-12-09 22:27 ` Kanoj Sarcar [this message]
1999-12-09 23:16 ` Ingo Molnar
1999-12-09 23:09 ` Benjamin C.R. LaHaise
1999-12-10 0:44 ` Ingo Molnar
1999-12-10 0:18 ` William J. Earl
1999-12-11 19:56 ` Stephen C. Tweedie
1999-12-10 12:21 ` Rik van Riel
1999-12-10 13:42 ` Ingo Molnar
1999-12-10 18:04 ` William J. Earl
1999-12-09 20:50 ` William J. Earl
1999-12-09 23:15 ` Ingo Molnar
1999-12-09 22:13 ` William J. Earl
1999-12-09 22:26 ` Alan Cox
1999-12-09 23:42 ` William J. Earl
1999-12-09 23:50 ` Alan Cox
1999-12-10 0:30 ` William J. Earl
1999-12-10 0:37 ` Alan Cox
1999-12-10 4:19 ` Oliver Xymoron
1999-12-10 10:14 ` Thomas Sailer
1999-12-09 23:24 ` Ingo Molnar
1999-12-09 22:33 ` Jeff Garzik
1999-12-09 23:32 ` Rogier Wolff
1999-12-09 23:44 ` JF Martinez
1999-12-10 0:52 ` Ingo Molnar
1999-12-09 23:46 ` Andi Kleen
1999-12-10 13:52 ` 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=199912092227.OAA10455@google.engr.sgi.com \
--to=kanoj@google.engr.sgi.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.rutgers.edu \
--cc=linux-mm@kvack.org \
--cc=mingo@chiara.csoma.elte.hu \
--cc=riel@nl.linux.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