From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Simon Kirby <sim@stormix.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 14:59:50 -0400 [thread overview]
Message-ID: <3905EB26.8DBFD111@mandrakesoft.com> (raw)
In-Reply-To: <20000425113616.A7176@stormix.com>
[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]
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.
The main reason is there is a noticeable performance increase when you
have so much more physical memory available for page and buffer cache.
I manually force this behavior now with the attached 'fillmem' program,
usually before a big compile on an otherwise quiet machine.
Jeff
--
Jeff Garzik | Nothing cures insomnia like the
Building 1024 | realization that it's time to get up.
MandrakeSoft, Inc. | -- random fortune
[-- Attachment #2: fillmem.c --]
[-- Type: text/plain, Size: 707 bytes --]
#include <stdio.h>
#include <stdlib.h>
#include <time.h>
#include <string.h>
#define MEGS 140
#define MEG (1024 * 1024)
int main (int argc, char *argv[])
{
void **data;
int i, r;
size_t megs = MEGS;
if ((argc >= 2) && (atoi(argv[1]) > 0))
megs = atoi(argv[1]);
data = malloc (megs * sizeof (void*));
if (!data) abort();
memset (data, 0, megs * sizeof (void*));
srand(time(NULL));
for (i = 0; i < megs; i++) {
data[i] = malloc(MEG);
memset (data[i], i, MEG);
printf("malloc/memset %03d/%03lu\n", i+1, megs);
}
for (i = megs - 1; i >= 0; i--) {
r = rand() % 200;
memset (data[i], r, MEG);
printf("memset #2 %03d/%03lu = %d\n", i+1, megs, r);
}
printf("done\n");
return 0;
}
next prev parent reply other threads:[~2000-04-25 18:59 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 [this message]
2000-04-25 19:06 ` Simon Kirby
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=3905EB26.8DBFD111@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=andrea@suse.de \
--cc=bcrl@redhat.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