From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: Mel Gorman <mel@csn.ul.ie>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Joel Schopp <jschopp@austin.ibm.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
lhms-devel@lists.sourceforge.net
Subject: Re: [Lhms-devel] Re: [PATCH 0/5] Reducing fragmentation using zones
Date: Fri, 20 Jan 2006 22:22:46 +0900 [thread overview]
Message-ID: <20060120222213.126F.Y-GOTO@jp.fujitsu.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0601201216280.14292@skynet>
Thanks! I'll try it next week. :-)
> On Fri, 20 Jan 2006, Yasunori Goto wrote:
>
> > > What sort of tests would you suggest? The tests I have been running to
> > > date are
> > >
> > > "kbuild + aim9" for regression testing
> > >
> > > "updatedb + 7 -j1 kernel compiles + highorder allocation" for seeing how
> > > easy it was to reclaim contiguous blocks
> >
> > BTW, is "highorder allocation test" your original test code?
> > If so, just my curious, I would like to see it too. ;-).
> >
>
> 1. Download http://www.csn.ul.ie/~mel/projects/vmregress/vmregress-0.20.tar.gz
> 2. Extract it to /usr/src/vmregress (i.e. there should be a
> /usr/src/vmregress/bin directory)
> 3. Download linux-2.6.11.tar.gz to /usr/src
> 4. Make a directory /usr/src/bench-stresshighalloc-test
> 5. cd to /usr/src/vmregress and run 3. cd to the directory and run
> ./configure --with-linux=/path/to/running/kernel
> make
>
> 5. Run the test
> bench-stresshighalloc.sh -z -k 6 --oprofile
>
> -z Will test using high memory
> -k 6 will build 1 kernel + 6 additional ones
> By default, it will try and allocate 275 order-10 pages. Specify the
> number of pages with -c and the order with -s
>
> The paths above are default paths. They can all be overridden with command
> line parameters like -t to specify a different kernel to use and -b to
> specify a different path to build all the kernels in.
>
> By default, the results will be logged to a directory whose name is based
> on the kernel being tested. For example, one result directory is
> ~/vmregressbench-2.6.16-rc1-mm1-clean/highalloc-heavy/log.txt
>
> Comparisions between different runs can be analysed by using
> diff-highalloc.sh. e.g.
>
> diff-highalloc.sh vmregressbench-2.6.16-rc1-mm1-clean vmregressbench-2.6.16-rc1-mm1-mbuddy-v22
>
> If you want to test just high-order allocations while some other workload
> is running, use bench-plainhighalloc.sh. See --help for a list of
> available options.
>
> If you want to use bench-aim9.sh, download and build aim9 in /usr/src/aim9
> and edit the s9workfile to specify the tests you are interested in. Use
> diff-aim9.sh to compare different runs of aim9.
>
> --
> Mel Gorman
> Part-time Phd Student Linux Technology Center
> University of Limerick IBM Dublin Software Lab
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Lhms-devel mailing list
> Lhms-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/lhms-devel
--
Yasunori Goto
--
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:[~2006-01-20 13:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-19 19:08 Mel Gorman
2006-01-19 19:08 ` [PATCH 1/5] Add __GFP_EASYRCLM flag and update callers Mel Gorman
2006-01-19 19:08 ` [PATCH 2/5] Create the ZONE_EASYRCLM zone Mel Gorman
2006-01-19 19:09 ` [PATCH 3/5] x86 - Specify amount of kernel memory at boot time Mel Gorman
2006-01-19 19:09 ` [PATCH 4/5] ppc64 " Mel Gorman
2006-01-19 19:09 ` [PATCH 5/5] ForTesting - Prevent OOM killer firing for high-order allocations Mel Gorman
2006-01-19 19:24 ` [PATCH 0/5] Reducing fragmentation using zones Joel Schopp
2006-01-20 0:13 ` [Lhms-devel] " KAMEZAWA Hiroyuki
2006-01-20 1:09 ` Mel Gorman
2006-01-20 1:25 ` KAMEZAWA Hiroyuki
2006-01-20 9:44 ` Mel Gorman
2006-01-20 10:40 ` KAMEZAWA Hiroyuki
2006-01-20 14:53 ` Mel Gorman
2006-01-20 18:10 ` Kamezawa Hiroyuki
2006-01-20 12:08 ` Yasunori Goto
2006-01-20 12:25 ` Mel Gorman
2006-01-20 13:22 ` Yasunori Goto [this message]
2006-01-20 0:42 ` Mel Gorman
2006-01-20 1:18 ` KAMEZAWA Hiroyuki
2006-01-20 12:03 ` Mel Gorman
2006-01-20 13:28 ` [Lhms-devel] " Yasunori Goto
2006-01-20 14:02 ` Mel Gorman
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=20060120222213.126F.Y-GOTO@jp.fujitsu.com \
--to=y-goto@jp.fujitsu.com \
--cc=jschopp@austin.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
/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