From: "Benjamin C.R. LaHaise" <blah@kvack.org>
To: Kanoj Sarcar <kanoj@google.engr.sgi.com>
Cc: linux-mm@kvack.org
Subject: Re: process selection
Date: Mon, 14 Jun 1999 13:46:02 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.3.96.990614133956.22744D-100000@mole.spellcast.com> (raw)
In-Reply-To: <199906141717.KAA31065@google.engr.sgi.com>
Sometime earlier, Rik wrote:
> > Could it be an idea to take the 'sleeping time' of each
> > process into account when selecting which process to swap
> > out? Due to extreme lack of free time, I'm asking what
> > you folks think of it before testing it myself...
On Mon, 14 Jun 1999, Kanoj Sarcar wrote:
> You are right, sleep time is a good heuristic to determine
> the "swappability" of a process.
I'm starting to think that going back and benchmarking my vm patches
against 2.1.47 or 66 might prove useful as they used a physical page
scanning with the old LFU technique, but proved remarkably faster than
scanning the virtual addresses space of processes. Gee, I guess it's time
for forward port the beast again and see what results it gets against
current things.
-ben (who now has another project for tonight)
--
To unsubscribe, send a message with 'unsubscribe linux-mm my@address'
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-06-14 17:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-12 20:00 Rik van Riel
1999-06-13 1:17 ` Andrea Arcangeli
1999-06-13 6:58 ` Rik van Riel
1999-06-14 17:17 ` Kanoj Sarcar
1999-06-14 17:46 ` Benjamin C.R. LaHaise [this message]
1999-06-14 19:26 ` Rik van Riel
1999-06-14 20:28 ` Benjamin C.R. LaHaise
1999-06-15 10:28 Antonino Sabetta
1999-06-17 23:25 ` 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=Pine.LNX.3.96.990614133956.22744D-100000@mole.spellcast.com \
--to=blah@kvack.org \
--cc=kanoj@google.engr.sgi.com \
--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