linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@conectiva.com.br>
To: Simon Kirby <sim@stormix.com>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
	Andrea Arcangeli <andrea@suse.de>,
	linux-mm@kvack.org, "Stephen C. Tweedie" <sct@redhat.com>,
	Ben LaHaise <bcrl@redhat.com>,
	linux-kernel@vger.rutgers.edu
Subject: Re: [PATCH] 2.3.99-pre6-3+  VM rebalancing
Date: Tue, 25 Apr 2000 16:34:24 -0300 (BRST)	[thread overview]
Message-ID: <Pine.LNX.4.21.0004251630180.10408-100000@duckman.conectiva> (raw)
In-Reply-To: <20000425120657.B7176@stormix.com>

On Tue, 25 Apr 2000, Simon Kirby wrote:

> Sorry, I made a mistake there while writing..I was going to give an
> example and wrote 60 seconds, but I didn't actually mean to limit
> anything to 60 seconds.  I just meant to make a really big global lru
> that contains everything including page cache and swap. :)

We already have that big global lru queue (actually, it's a 
bit more closer to second chance replacement).

For pages which are in the page tables of processes, we
put the pages on the queue when we scan them and they
weren't used since we scanned them the last time (NRU
replacement). After that, they go through the lru queue
and are reclaimed when it's their turn.

regards,

Rik
--
The Internet is not a network of computers. It is a network
of people. That is its real strength.

Wanna talk about the kernel?  irc.openprojects.net / #kernelnewbies
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-04-25 19:34 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-23  2:08 Rik van Riel
2000-04-25  1:25 ` Simon Kirby
2000-04-25 15:09   ` Rik van Riel
2000-04-25 15:59     ` Andrea Arcangeli
2000-04-25 17:20       ` Rik van Riel
2000-04-25 18:36         ` Simon Kirby
2000-04-25 18:59           ` Jeff Garzik
2000-04-25 19:06             ` Simon Kirby
2000-04-25 19:34               ` Rik van Riel [this message]
2000-04-26 11:01               ` Stephen C. Tweedie
2000-04-26 11:15                 ` Rik van Riel
2000-04-26 12:29                   ` Stephen C. Tweedie
2000-04-26 12:45                     ` David S. Miller
2000-04-26 11:25                 ` David S. Miller
2000-04-26 13:00                   ` Stephen C. Tweedie
2000-04-26 13:11                     ` David S. Miller
2000-04-26 15:23                       ` Stephen C. Tweedie
2000-04-26 15:25                         ` David S. Miller
2000-04-26 16:09                           ` Stephen C. Tweedie
2000-04-27 20:28                           ` Simon Kirby
2000-04-27 22:32                           ` Jamie Lokier
2000-04-26 13:46                   ` Rik van Riel
2000-04-26 14:33                     ` David S. Miller
2000-04-26 16:31                       ` Andi Kleen
2000-04-26 15:28                         ` David S. Miller
2000-04-26 15:41                           ` Andi Kleen

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.0004251630180.10408-100000@duckman.conectiva \
    --to=riel@conectiva.com.br \
    --cc=andrea@suse.de \
    --cc=bcrl@redhat.com \
    --cc=jgarzik@mandrakesoft.com \
    --cc=linux-kernel@vger.rutgers.edu \
    --cc=linux-mm@kvack.org \
    --cc=riel@nl.linux.org \
    --cc=sct@redhat.com \
    --cc=sim@stormix.com \
    /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