From: Nick Piggin <piggin@cyberone.com.au>
To: Andrew Morton <akpm@osdl.org>
Cc: Nikita Danilov <Nikita@Namesys.COM>, linux-mm@kvack.org
Subject: [BENCHMARKS] 2.6 kbuild results (with add_to_swap patch)
Date: Fri, 30 Jan 2004 13:53:29 +1100 [thread overview]
Message-ID: <4019C729.8050505@cyberone.com.au> (raw)
In-Reply-To: <20040128134425.0c00fb2f.akpm@osdl.org>
Andrew Morton wrote:
>Nikita Danilov <Nikita@Namesys.COM> wrote:
>
>>Hello,
>>
>>shrink_list() checks PageSwapCache() before calling add_to_swap(), this
>>means that anonymous page that is going to be added to the swap right
>>now these checks return false and:
>>
>> (*) it will be unaccounted for in nr_mapped, and
>>
>> (*) it won't be written to the swap if gfp_flags include __GFP_IO but
>> not __GFP_FS.
>>
>>(Both will happen only on the next round of scanning.)
>>
>
>OK. Does it make a measurable change in any benchmarks?
>
>
Small big significantly better on kbuild when tested on top of the other
two patches (dont-rotate-active-list and my mapped-fair).
With this patch as well, we are now as good or better than 2.4 on
medium and heavy swapping kbuilds and much better than stock 2.6
with light swapping loads (not as good as 2.4 but close).
http://www.kerneltrap.org/~npiggin/vm/3/
--
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:[~2004-01-30 2:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-28 16:43 [PATCH] mm/vmscan.c:shrink_list(): check PageSwapCache() after add_to_swap() Nikita Danilov
2004-01-28 21:44 ` Andrew Morton
2004-01-30 2:53 ` Nick Piggin [this message]
2004-01-30 12:04 ` [BENCHMARKS] 2.6 kbuild results (with add_to_swap patch) Rik van Riel
2004-01-31 1:19 ` Nick Piggin
2004-01-31 1:29 ` Andrew Morton
2004-01-31 1:34 ` Nick Piggin
2004-02-04 5:11 ` Nick Piggin
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=4019C729.8050505@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=Nikita@Namesys.COM \
--cc=akpm@osdl.org \
--cc=linux-mm@kvack.org \
/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