Note numad will attempt to manage / balance processes after they're
launched, but the ideal case is libvirt pre-places them in a good spot
and they never move
On 03/07/2012 10:38 AM, Osier Yang wrote:
On 2012年03月07日 21:48, Daniel P. Berrange wrote:
On Wed, Mar 07, 2012 at 09:55:16PM
to
always pass a memory amount to numad command line, it may be
not good in some case. @Bill(s), correct me if I'm not right. :-)
Perhaps we could have a bool attribute then, such as:
cpu required_cpus=4 required_memory=yes|no/
Please keep Bill Gray on this thread. He is the author of numad
Hi Daniel,
How can we get NUMA-aligned memory and CPUs if we apply binding APIs
after the process has already started? Might not all the memory
already be allocated on the wrong nodes by then?
For expert users, what are the problems with starting qemu with an
external numactl command
Thanks for the feedback Lee!
One reason to use membind instead of preferred is that one can
prefer only a single node. For large guests, you can specify multiple
nodes with membind. I think preferred would be preferred if it
allowed multiple nodes.
- Bill
On 05/05/2011 10:33 AM, Lee
