From: Benjamin LaHaise <bcrl@kvack.org>
To: linux-mm@kvack.org
Subject: Re: Slow memory support
Date: Thu, 18 Dec 1997 01:00:12 -0500 (U\x01) [thread overview]
Message-ID: <Pine.LNX.3.95.971218005832.7940A-100000@as200.spellcast.com> (raw)
From: Rik van Riel <H.H.vanRiel@fys.ruu.nl>
X-Sender: riel@mirkwood.dummy.home
Reply-To: H.H.vanRiel@fys.ruu.nl
To: Pavel Machek <pavel@Elf.mj.gts.cz>
cc: linux-mm <linux-mm@kvack.org>
Subject: Re: Slow memory support
In-Reply-To: <19971217221622.50179@Elf.mj.gts.cz>
Message-ID: <Pine.LNX.3.91.971218000718.887B-100000@mirkwood.dummy.home>
Approved: ObHack@localhost
Organization: none
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Wed, 17 Dec 1997, Pavel Machek wrote:
> This is what I do. (I only put buffers there, for now). But, what
> about you have 64Meg of normal and 64Meg of slow memory? I doubt
> you'll find 64Meg worth of buffers and page tables.
Hmm, what about putting everything in slow memory, except
for executable code...
Or (with Ben's patch) we could move 'overly active' pages
to fast memory and other pages to slow memory, with a max
amount of pages we could move every second.
Rik.
+-----------------------------+------------------------------+
| For Linux mm-patches, go to | "I'm busy managing memory.." |
| my homepage (via LinuxHQ). | H.H.vanRiel@fys.ruu.nl |
| ...submissions welcome... | http://www.fys.ruu.nl/~riel/ |
+-----------------------------+------------------------------+
next reply other threads:[~1997-12-18 6:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-18 6:00 Benjamin LaHaise [this message]
[not found] <19971217221622.50179@Elf.mj.gts.cz>
[not found] ` <Pine.LNX.3.91.971218000718.887B-100000@mirkwood.dummy.home>
1997-12-18 13:34 ` Pavel Machek
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=Pine.LNX.3.95.971218005832.7940A-100000@as200.spellcast.com \
--to=bcrl@kvack.org \
--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