From: Roger Luethi <rl@hellgate.ch>
To: William Lee Irwin III <wli@holomorphy.com>,
Rik van Riel <riel@redhat.com>,
linux-mm@kvack.org, Andrew Morton <akpm@digeo.com>
Subject: Re: load control demotion/promotion policy
Date: Tue, 23 Dec 2003 17:13:23 +0100 [thread overview]
Message-ID: <20031223161323.GA6082@k3.hellgate.ch> (raw)
In-Reply-To: <20031222012126.GC11655@holomorphy.com>
On Sun, 21 Dec 2003 17:21:26 -0800, William Lee Irwin III wrote:
> Obviously, the simple regressions should be corrected first. We're not
> interested in programming them ourselves because as far as we know,
> you've already written the fixes. It would be premature to do
Sorry about the delay. Buried in work.
I wonder how I managed to make that impression. I created one patch as
a proof of concept. It demonstrates that the data I collected can be
used to identify regressions and -- sometimes -- roll them back.
I repeated the benchmarks just to be sure. Numbers are not accurate
(2.6.0 performance has a huge variance), but quite reliable
nevertheless. I should do more runs, but 10 is about as many as I can
get done in time. Median run time (in seconds) for each benchmark are
as follows (priority, kswapd_throttling refer to the two hunks in the
patch below):
efax kbuild qsbench
2.6.0 vanilla
865 500 275
priority
860 491 299
kswapd_throttling
659 500 362
priority + kswapd_throttling
560 433 327
The numbers look pretty good, but the patch is lame. It does not even
properly revert the distress changes let alone deal with the issue the
changes in 2.6.0-test3 were supposed to address.
That's the only patch I have reasonably solid data for.
Roger
diff -uNp -X /home/rl/data/doc/kernel/dontdiff-2.6 /data/exp/tmp/18_binsearch/linux-2.6.0/mm/vmscan.c ./mm/vmscan.c
--- /data/exp/tmp/18_binsearch/linux-2.6.0/mm/vmscan.c Wed Oct 15 15:03:46 2003
+++ ./mm/vmscan.c Tue Dec 23 08:25:42 2003
@@ -632,7 +632,7 @@ refill_inactive_zone(struct zone *zone,
* `distress' is a measure of how much trouble we're having reclaiming
* pages. 0 -> no problems. 100 -> great trouble.
*/
- distress = 100 >> zone->prev_priority;
+ distress = 100 >> priority;
/*
* The point of this algorithm is to decide when to start reclaiming
@@ -981,8 +981,7 @@ static int balance_pgdat(pg_data_t *pgda
}
if (all_zones_ok)
break;
- if (to_free > 0)
- blk_congestion_wait(WRITE, HZ/10);
+ blk_congestion_wait(WRITE, HZ/10);
}
for (i = 0; i < pgdat->nr_zones; i++) {
--
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-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2003-12-23 16:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-21 2:33 Rik van Riel
2003-12-21 14:15 ` William Lee Irwin III
2003-12-21 23:55 ` Roger Luethi
2003-12-22 1:21 ` William Lee Irwin III
2003-12-23 16:13 ` Roger Luethi [this message]
2003-12-22 1:34 ` Rik van Riel
2003-12-23 16:13 ` Roger Luethi
2003-12-22 6:56 ` Andrew Morton
2003-12-23 16:14 ` Roger Luethi
2003-12-22 7:00 ` William Lee Irwin III
2003-12-22 15:12 ` Benjamin LaHaise
2003-12-22 15:18 ` William Lee Irwin III
2003-12-22 15:22 ` Benjamin LaHaise
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=20031223161323.GA6082@k3.hellgate.ch \
--to=rl@hellgate.ch \
--cc=akpm@digeo.com \
--cc=linux-mm@kvack.org \
--cc=riel@redhat.com \
--cc=wli@holomorphy.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