From: "KOSAKI Motohiro" <kosaki.motohiro@jp.fujitsu.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Johannes Weiner <hannes@saeurebad.de>,
Rik van Riel <riel@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Nossum <vegard.nossum@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm] mm: more likely reclaim MADV_SEQUENTIAL mappings
Date: Mon, 21 Jul 2008 12:53:23 +0900 [thread overview]
Message-ID: <2f11576a0807202053m858ef54r68e9ba637801e9e0@mail.gmail.com> (raw)
In-Reply-To: <20080720184843.9f7b48e9.akpm@linux-foundation.org>
Hi Andrew,
>> in my experience,
>> - page_referenced_one is performance critical point.
>> you should test some benchmark.
>> - its patch improved mmaped-copy performance about 5%.
>> (Of cource, you should test in current -mm. MM code was changed widely)
>>
>> So, I'm looking for your test result :)
>
> The change seems logical and I queued it for 2.6.28.
Great.
> But yes, testing for what-does-this-improve is good and useful, but so
> is testing for what-does-this-worsen. How do we do that in this case?
In general, page_referenced_one is important for reclaim throuput.
if crap page_referenced_one changing happend,
system reclaim throuput become slow down.
Of cource, I don't think this patch cause performance regression :-)
So, any benchmark with memcgroup memory restriction is good choice.
btw:
maybe, I will able to post mamped-copy improve mesurement of Johannes's patch
after OLS.
--
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-07-21 3:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-19 17:31 Johannes Weiner
2008-07-19 17:59 ` Rik van Riel
2008-07-21 0:09 ` KOSAKI Motohiro
2008-07-21 1:48 ` Andrew Morton
2008-07-21 3:53 ` KOSAKI Motohiro [this message]
2008-07-21 5:49 ` Nick Piggin
2008-07-21 15:14 ` Rik van Riel
2008-07-22 2:02 ` Nick Piggin
2008-07-22 2:36 ` Rik van Riel
2008-07-22 2:54 ` Nick Piggin
2008-07-22 3:04 ` Rik van Riel
2008-07-22 3:43 ` Nick Piggin
2008-07-22 3:49 ` 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=2f11576a0807202053m858ef54r68e9ba637801e9e0@mail.gmail.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@saeurebad.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=vegard.nossum@gmail.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