linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@conectiva.com.br>
To: Benjamin Redelings I <bredelin@ucla.edu>
Cc: linux-mm@kvack.org
Subject: Re: Happiness with t8-vmpatch4 (was Re:  Does page-aging really work?)
Date: Sat, 16 Sep 2000 04:57:55 -0300 (BRST)	[thread overview]
Message-ID: <Pine.LNX.4.21.0009160455260.1519-100000@duckman.distro.conectiva> (raw)
In-Reply-To: <39C31C9F.1C202CD8@ucla.edu>

On Sat, 16 Sep 2000, Benjamin Redelings I wrote:

>    1. test8-vmpatch4 does not swap very much at first, but then
> swaps a lot of memory in a short time when triggered.

>   2. I guess we could wish that unused programs got swapped a
> bit sooner instead of all at once - but presumably that can be
> tuned.

This is indeed something to look at. Maybe we could give
idle processes (sleeping for more than 20 seconds?) a
"full" swap_cnt instead of swap_cnt = rss >> SWAP_SHIFT ?

And we could also start swapping a bit earlier when the
cache is getting small, but I'm not sure about how to
do this or exactly what performance benefits that would
give ...

regards,

Rik
--
"What you're running that piece of shit Gnome?!?!"
       -- Miguel de Icaza, UKUUG 2000

http://www.conectiva.com/		http://www.surriel.com/

--
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.eu.org/Linux-MM/

  reply	other threads:[~2000-09-16  7:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-09-08 21:34 Multiqueue VM Patch OK? Does page-aging really work? Benjamin Redelings I
2000-09-08 22:58 ` Rik van Riel
2000-09-16  7:09   ` Happiness with t8-vmpatch4 (was Re: Does page-aging really work?) Benjamin Redelings I
2000-09-16  7:57     ` Rik van Riel [this message]
2000-09-16 18:20       ` Benjamin Redelings I
2000-09-16 18:22         ` Rik van Riel

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.4.21.0009160455260.1519-100000@duckman.distro.conectiva \
    --to=riel@conectiva.com.br \
    --cc=bredelin@ucla.edu \
    --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