From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: minchan Kim <barrioskmc@gmail.com>
Cc: kosaki.motohiro@jp.fujitsu.com,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
Rik van Riel <riel@redhat.com>,
Lee Schermerhorn <Lee.Schermerhorn@hp.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] the proposal of improve page reclaim by throttle
Date: Wed, 20 Feb 2008 18:24:19 +0900 [thread overview]
Message-ID: <20080220181447.6444.KOSAKI.MOTOHIRO@jp.fujitsu.com> (raw)
In-Reply-To: <44c63dc40802200056va847417v1cfc847341bb8cc0@mail.gmail.com>
Hi Kim-san
Do you adjust hackbench parameter?
my parameter adjust my test machine(8GB mem),
if unchanged, maybe doesn't works it because lack memory.
> I am a many interested in your patch. so I want to test it with exact
> same method as you did.
> I will test it in embedded environment(ARM 920T, 32M ram) and my
> desktop machine.(Core2Duo 2.2G, 2G ram)
Hm
I don't have embedded test machine.
but I can desktop.
I will test it about weekend.
if you don't mind, could you please send me .config file
and tell me your test kernel version?
Thanks, interesting report.
> I guess this patch won't be efficient in embedded environment.
> Since many embedded board just have one processor and don't have any
> swap device.
reclaim conflict rarely happened on UP.
thus, my patch expect no improvement.
but (of course) I will fix regression.
> So, How do I evaluate following field as you did ?
>
> * elapse (what do you mean it ??)
> * major fault
/usr/bin/time command output that.
> * max parallel reclaim tasks:
> * max consumption time of
> try_to_free_pages():
sorry, I inserted debug code to my patch at that time.
--
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-02-20 9:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 5:44 KOSAKI Motohiro
2008-02-19 6:34 ` Nick Piggin
2008-02-19 7:09 ` KOSAKI Motohiro
2008-02-19 13:31 ` Rik van Riel
2008-02-20 8:56 ` minchan Kim
2008-02-20 9:24 ` KOSAKI Motohiro [this message]
2008-02-20 9:49 ` minchan Kim
2008-02-20 10:09 ` KOSAKI Motohiro
2008-02-21 9:38 ` minchan Kim
2008-02-21 10:55 ` KOSAKI Motohiro
2008-02-21 12:29 ` minchan Kim
2008-02-21 12:41 ` KOSAKI Motohiro
2008-02-21 9:48 ` Balbir Singh
2008-02-21 11:01 ` KOSAKI Motohiro
2008-02-21 11:02 ` Balbir Singh
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=20080220181447.6444.KOSAKI.MOTOHIRO@jp.fujitsu.com \
--to=kosaki.motohiro@jp.fujitsu.com \
--cc=Lee.Schermerhorn@hp.com \
--cc=balbir@linux.vnet.ibm.com \
--cc=barrioskmc@gmail.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.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