From: Rik van Riel <riel@conectiva.com.br>
To: Ed Tomlinson <tomlins@cam.org>
Cc: linux-mm@kvack.org, squash@primary.net
Subject: Re: Fwd: Re: [PATCH][RFC] appling preasure to icache and dcache
Date: Tue, 3 Apr 2001 18:35:28 -0300 (BRST) [thread overview]
Message-ID: <Pine.LNX.4.21.0104031832540.14090-100000@imladris.rielhome.conectiva> (raw)
In-Reply-To: <01040317251303.31476@oscar>
On Tue, 3 Apr 2001, Ed Tomlinson wrote:
> On Tuesday 03 April 2001 11:03, Benjamin Redelings I wrote:
> > Hi, I'm glad somebody is working on this! VM-time seems like a pretty
> > useful concept.
>
> Think it might be useful for detecting trashing too. If vmtime is
> made to directly relate to the page allocation rate then you can do
> something like this. Let K be a number intially representing 25% of
> ram pages. Because vmtime is directly releated to allocation rates its
> meanful to subtract K from the current vmtime. For each swapped out
> page, record the current vmtime. Now if the recorded vmtime of the
> page you are swapping in is greater than vmtime-K increment A
> otherwise increment B. If A>B we are thrashing. We decay A and B via
> kswapd. We adjust K depending on the swapping rate. Thoughts?
Hmmm, how exactly would this algorithm work ?
>From your description above, I can't quite see how it would
work (or why it would work).
regards,
Rik
--
Virtual memory is like a game you can't win;
However, without VM there's truly nothing to lose...
http://www.surriel.com/
http://www.conectiva.com/ http://distro.conectiva.com.br/
--
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/
next prev parent reply other threads:[~2001-04-03 21:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-03 21:25 Ed Tomlinson
2001-04-03 21:35 ` Rik van Riel [this message]
2001-04-03 23:50 ` Ed Tomlinson
2001-04-04 12:40 ` sfkaplan
2001-04-05 11:35 ` Ed Tomlinson
2001-04-05 14:46 ` 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.0104031832540.14090-100000@imladris.rielhome.conectiva \
--to=riel@conectiva.com.br \
--cc=linux-mm@kvack.org \
--cc=squash@primary.net \
--cc=tomlins@cam.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