From: Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Mel Gorman <mel@csn.ul.ie>
Cc: Joel Schopp <jschopp@austin.ibm.com>,
Linux Memory Management List <linux-mm@kvack.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
lhms-devel@lists.sourceforge.net
Subject: Re: [Lhms-devel] Re: [PATCH 0/5] Reducing fragmentation using zones
Date: Sat, 21 Jan 2006 03:10:43 +0900 [thread overview]
Message-ID: <43D127A3.1010200@jp.fujitsu.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0601201204100.14292@skynet>
Mel Gorman wrote:
> On Fri, 20 Jan 2006, KAMEZAWA Hiroyuki wrote:
>>1. Using 1000+ processes(threads) at once
>
>
> Would tiobench --threads be suitable or would the IO skew what you are
> looking for? If the IO is a problem, what would you recommend instead?
>
What I'm looking for is slab usage coming with threads/procs.
>
>>2. heavy network load.
>
>
> Would iperf be suitable?
>
maybe
>
>>3. running NFS
>
>
> Is running a kernel build over NFS reasonable? Should it be a remote NFS
> server or could I setup a NFS share and mount it locally? If a kernel
> build is not suitable, would tiobench over NFS be a better plan?
>
I considered doing kernel build on NFS which is mounted localy.
> The scenario people really care about (someone correct me if I'm wrong
> here) for hot-remove is giving virtual machines more or less memory as
> demand requires. In this case, the "big" area of memory required is the
> same size as a sparsemem section - 16MiB on the ppc64 and 64MiB on the x86
> (I think). Also, for hot-remove, it does not really matter where in the
> zone the chunk is, as long as it is free. For ppc64, 16MiB of contiguous
> memory is reasonably easy to get with the list-based approach and the case
> would likely be the same for x86 if the value of MAX_ORDER was increased.
>
What I' want is just node-hotplug on NUMA, removing physical range of mem.
So I'll need and push dividing memory into removable zones or pgdat, anyway.
For people who just want resizing, what you say is main reason for hotplug.
-- Kame
--
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 18:10 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 [this message]
2006-01-20 12:08 ` Yasunori Goto
2006-01-20 12:25 ` Mel Gorman
2006-01-20 13:22 ` Yasunori Goto
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=43D127A3.1010200@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=jschopp@austin.ibm.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