From: "KOSAKI Motohiro" <kosaki.motohiro@jp.fujitsu.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Rik van Riel <riel@redhat.com>
Cc: kosaki.motohiro@jp.fujitsu.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Peter Zijlstra <peterz@infradead.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Christoph Lameter <cl@linux-foundation.org>,
Nick Piggin <npiggin@suse.de>
Subject: Re: [PATCH] vmscan: skip freeing memory from zones with lots free
Date: Tue, 9 Dec 2008 02:48:40 +0900 [thread overview]
Message-ID: <2f11576a0812080948k135e15c5h2bc727355235f94@mail.gmail.com> (raw)
In-Reply-To: <20081208220016.53FB.KOSAKI.MOTOHIRO@jp.fujitsu.com>
> example,
>
> Called zone_watermark_ok(zone, 2, pages_min, 0, 0);
> pages_min = 64
> free pages = 80
>
> case A.
>
> order nr_pages
> --------------------
> 2 5
> 1 10
> 0 30
>
> -> zone_watermark_ok() return 1
>
> case B.
>
> order nr_pages
> --------------------
> 3 10
> 2 0
> 1 0
> 0 0
>
> -> zone_watermark_ok() return 0
Doh!
this example is obiously buggy.
I guess Mr. KOSAKI is very silly or Idiot.
I recommend to he get feathery blanket and good sleeping, instead
black black coffee ;-)
...but below mesurement result still true.
> This patch change zone_watermark_ok() logic to prefer large contenious block.
>
>
> Result:
>
> test machine:
> CPU: ia64 x 8
> MEM: 8GB
>
> benchmark:
> $ tbench 8 (three times mesurement)
>
> tbench works between about 600sec.
> alloc_pages() and zone_watermark_ok() are called about 15,000,000 times.
>
>
> 2.6.28-rc6 this patch
>
> throughput max-latency throughput max-latency
> ---------------------------------------------------------
> 1480.92 20.896 1,490.27 19.606
> 1483.94 19.202 1,482.86 21.082
> 1478.93 22.215 1,490.57 23.493
>
> avg 1,481.26 20.771 1,487.90 21.394
> std 2.06 1.233 3.56 1.602
> min 1,478.93 19.202 1,477.86 19.606
> max 1,483.94 22.215 1,490.57 23.493
>
>
> throughput improve about 5MB/sec. it over measurement wobbly.
--
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:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-12-08 17:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-28 11:08 Rik van Riel
2008-11-28 11:30 ` Peter Zijlstra
2008-11-28 22:43 ` Johannes Weiner
2008-11-29 7:19 ` Andrew Morton
2008-11-29 10:55 ` KOSAKI Motohiro
2008-12-08 13:00 ` KOSAKI Motohiro
2008-12-08 13:03 ` KOSAKI Motohiro
2008-12-08 17:48 ` KOSAKI Motohiro [this message]
2008-12-10 5:07 ` Nick Piggin
2008-12-08 20:25 ` Rik van Riel
2008-12-10 5:09 ` Nick Piggin
2008-12-12 5:50 ` KOSAKI Motohiro
2008-11-29 16:47 ` Rik van Riel
2008-11-29 17:45 ` Andrew Morton
2008-11-29 17:58 ` Rik van Riel
2008-11-29 18:26 ` Andrew Morton
2008-11-29 18:41 ` Rik van Riel
2008-11-29 18:51 ` Andrew Morton
2008-11-29 18:59 ` Rik van Riel
2008-11-29 20:29 ` Andrew Morton
2008-11-29 21:35 ` Rik van Riel
2008-11-29 21:57 ` Andrew Morton
2008-11-29 22:07 ` Rik van Riel
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=2f11576a0812080948k135e15c5h2bc727355235f94@mail.gmail.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=npiggin@suse.de \
--cc=peterz@infradead.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