On Fri, 20 Jan 2006, KAMEZAWA Hiroyuki wrote:What I'm looking for is slab usage coming with threads/procs.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?
maybe
2. heavy network load.
Would iperf be suitable?
I considered doing kernel build on NFS which is mounted localy.
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?
The scenario people really care about (someone correct me if I'm wrongWhat I' want is just node-hotplug on NUMA, removing physical range of mem.
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.