From: Simon Kirby <sim@stormix.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: riel@nl.linux.org, 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 12:06:58 -0700 [thread overview]
Message-ID: <20000425120657.B7176@stormix.com> (raw)
In-Reply-To: <3905EB26.8DBFD111@mandrakesoft.com>; from jgarzik@mandrakesoft.com on Tue, Apr 25, 2000 at 02:59:50PM -0400
On Tue, Apr 25, 2000 at 02:59:50PM -0400, Jeff Garzik wrote:
> Simon Kirby wrote:
> > Hrmm.. I guess the ideal solution would be that swappable pages would age
> > just like cache pages and everything else? Then, if a particular
> > program's page hasn't been accessed for 60 seconds and there is nothing
> > older in the page cahce, it would swap out...
>
> Again a policy decision... I think such a feature should be present and
> enabled by default, but there are some people who would prefer that
> their configuration not do this, or would prefer that the timeout for
> old pages be far longer than 60 seconds.
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. :)
Simon-
[ Stormix Technologies Inc. ][ NetNation Communications Inc. ]
[ sim@stormix.com ][ sim@netnation.com ]
[ Opinions expressed are not necessarily those of my employers. ]
--
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:[~2000-04-25 19:06 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 [this message]
2000-04-25 19:34 ` Rik van Riel
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=20000425120657.B7176@stormix.com \
--to=sim@stormix.com \
--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 \
/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