From: Nick Piggin <piggin@cyberone.com.au>
To: Rik van Riel <riel@redhat.com>
Cc: Andrew Morton <akpm@osdl.org>,
Nikita Danilov <Nikita@Namesys.COM>,
linux-mm@kvack.org
Subject: Re: [BENCHMARKS] 2.6 kbuild results (with add_to_swap patch)
Date: Wed, 04 Feb 2004 16:11:06 +1100 [thread overview]
Message-ID: <40207EEA.90605@cyberone.com.au> (raw)
In-Reply-To: <Pine.LNX.4.44.0401300704130.20553-100000@chimarrao.boston.redhat.com>
Rik van Riel wrote:
>On Fri, 30 Jan 2004, Nick Piggin wrote:
>
>
>>Small big significantly better on kbuild when tested on top of the other
>>two patches (dont-rotate-active-list and my mapped-fair).
>>
>
>Where can I grab those ?
>
>
>>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/
>>
>
>Neat! Does it have any side effects to interactive
>desktop behaviour ?
>
>
Hi Rik,
I've just tried the latest patchset on my desktop system. Doing
a make -j4 bzImage, hdparm -t /dev/hda in a loop, mozilla, gnome
xterms etc.
Nothing bad is happening, although I'm only just touching swap.
--
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>
prev parent reply other threads:[~2004-02-04 5:11 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 ` [BENCHMARKS] 2.6 kbuild results (with add_to_swap patch) Nick Piggin
2004-01-30 12:04 ` 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 [this message]
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=40207EEA.90605@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=Nikita@Namesys.COM \
--cc=akpm@osdl.org \
--cc=linux-mm@kvack.org \
--cc=riel@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