linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <H.H.vanRiel@fys.ruu.nl>
To: Pavel Machek <pavel@Elf.mj.gts.cz>
Cc: linux-mm <linux-mm@kvack.org>
Subject: Re: pageable page tables
Date: Tue, 9 Dec 1997 15:41:23 +0100 (MET)	[thread overview]
Message-ID: <Pine.LNX.3.91.971209153832.584E-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <19971209122346.02899@Elf.mj.gts.cz>

On Tue, 9 Dec 1997, Pavel Machek wrote:

> > > Simple task might be 'memory priorities'. Something like priorities
> > > for scheduler but for memory. (I tried to implement them, and they
> > > gave <1% performance gain ;-), but I have interface to set such
> > > parameter if you want to play).
> > 
> > sounds rather good... (swapout-priorities??)
> 
> But proved to be pretty ineffective. I came to this idea when I
> realized that to cook machine, running 100 processes will not hurt too
> much. But running 10 processes, 50 megabytes each will cook almost
> anything...

what about:

if (page->age - p->mem_priority)
	exit 0 / goto next;
else {
	get_rid_of(page);
	and_dont_show_your_face_again_for_some_time(page);
}

effectively putting the program to sleep if:
- this page faults again soon
- memory is still tight

hmm, just an idea...

Rik.

--
Send Linux memory-management wishes to me: I'm currently looking
for something to hack...

  parent reply	other threads:[~1997-12-09 15:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <19971209122346.02899@Elf.mj.gts.cz>
1997-12-09 14:37 ` Rik van Riel
1997-12-09 14:41 ` Rik van Riel [this message]
1997-12-18  6:01 Benjamin LaHaise
     [not found] <19971210161108.02428@Elf.mj.gts.cz>
1997-12-12  6:57 ` Rik van Riel
1997-12-17 21:14   ` Pavel Machek
     [not found]     ` <Pine.LNX.3.91.971218000000.887A-100000@mirkwood.dummy.home>
1997-12-18 13:33       ` Pavel Machek
     [not found] <Pine.LNX.3.95.971126091603.8295A-100000@gwyn.tux.org>
1997-11-27 13:07 ` Rik van Riel
1997-11-27 18:23   ` Alan Cox
1997-11-27 18:56     ` Chris Evans

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.91.971209153832.584E-100000@mirkwood.dummy.home \
    --to=h.h.vanriel@fys.ruu.nl \
    --cc=linux-mm@kvack.org \
    --cc=pavel@Elf.mj.gts.cz \
    /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