From: Daniel Phillips <phillips@bonn-fries.net>
To: linux-mm@kvack.org
Cc: Rik van Riel <riel@conectiva.com.br>,
Marcelo Tosatti <marcelo@conectiva.com.br>
Subject: [RFC] Accelerate dbench
Date: Sun, 5 Aug 2001 02:04:59 +0200 [thread overview]
Message-ID: <01080502045901.00315@starship> (raw)
This simple patch to 2.4.8-pre4 accelerates dbench quite spectacularly
for me. It also slows down my more realistic make+grep load, so it's
not generally a good thing, but... if we could detect the conditions
where this activation strategy is desirable, it could turn into a good
thing.
This doesn't address any burning issue at the moment, it's just for
comment. Note that it effectively turns check_used_once into a no-op.
The effect of the patch is to always activate pages when they are
successfully looked up, not when first created. This allows unused
readahead pages to be quickly reclaimed. (Buffer pages could easily
be treated the same way but I didn't try it.) Together with -pre4's
shorter IO queue (also probably not a good thing, as Linus pointed
out) this seems to be very friendly to dbench, for reasons I still
don't understand.
With this patch, I saw very large flucuations in the timings obtained
from dbench 12 on this 64 MB Vaio, but the times ranged from good to
excellent, varying by about 30%. This is with identical running
conditions, starting from a clean reboot each time, and mkfs'ing the
test partition. Go figure. As always, the best dbench times were
associated with very unfair scheduling, with frequent bursts where a
single process makes rapid progress and the others appear to be
pushed aside.
--- ../2.4.7.clean/mm/filemap.c Sat Aug 4 14:27:16 2001
+++ ./mm/filemap.c Sat Aug 4 14:32:51 2001
@@ -307,9 +307,9 @@
if (page->index == offset)
break;
}
- /* Mark the page referenced, kswapd will find it later. */
SetPageReferenced(page);
-
+ if (!PageActive(page))
+ activate_page(page);
not_found:
return page;
}
--
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/
next reply other threads:[~2001-08-05 0:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-05 0:04 Daniel Phillips [this message]
2001-08-05 0:02 ` Rik van Riel
2001-08-05 2:33 ` Daniel Phillips
2001-08-05 2:39 ` Rik van Riel
2001-08-06 17:20 ` Daniel Phillips
2001-08-06 0:28 ` Andrew Morton
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=01080502045901.00315@starship \
--to=phillips@bonn-fries.net \
--cc=linux-mm@kvack.org \
--cc=marcelo@conectiva.com.br \
--cc=riel@conectiva.com.br \
/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