From: Andrew Morton <akpm@osdl.org>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: linux-mm@kvack.org, Nikita@Namesys.COM
Subject: Re: More vm benchmarking
Date: Wed, 25 Feb 2004 01:47:57 -0800 [thread overview]
Message-ID: <20040225014757.4c79f2af.akpm@osdl.org> (raw)
In-Reply-To: <403C66D2.6010302@cyberone.com.au>
Nick Piggin <piggin@cyberone.com.au> wrote:
>
> kernel | run | -j5 | -j10 | -j15 |
> 2.6.3 1 136 886 2511
> 2.6.3 2 150 838 2465
>
> -mm2 1 136 646 1484
> -mm2 2 142 676 1265
>
> -mm3 1 135 881 1828
> -mm3 2 146 790 1844
>
> This quite clearly shows your patches hurting as I told you.
Probably. But these differences are small, relative to some differences
wrt 2.4.x
> Why did it get slower?
Dunno. Maybe the workload prefers imbalanced zone scanning.
> I assume it is because the batching patch places uneven
> pressure on normal and DMA zones.
The patch improves highmem-vs-lowmem balancing from 10:1 to 1:1. What
makes you think that it worsens ZONE_NORMAL-vs-ZONE_DMA balancing?
It's easy enough to instrument - just split pgsteal_lo into pgsteal_normal
and pgsteal_dma.
--
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-02-25 9:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 9:11 Nick Piggin
2004-02-25 9:21 ` Nick Piggin
2004-02-25 9:47 ` Andrew Morton [this message]
2004-02-25 9:57 ` Nick Piggin
2004-02-25 10:04 ` Andrew Morton
2004-02-25 11:50 ` Andrew Morton
2004-02-26 0:51 ` Nick Piggin
2004-02-26 1:14 ` Andrew Morton
2004-02-26 1:35 ` Nick Piggin
2004-02-26 1:57 ` Andrew Morton
2004-02-26 2:04 ` 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=20040225014757.4c79f2af.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=Nikita@Namesys.COM \
--cc=linux-mm@kvack.org \
--cc=piggin@cyberone.com.au \
/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