Lenny Verkhovsky wrote:
Actually the size is suppose to be the same,
Yes, I would think that that is how it is supposed to work.
It just suppose to bind process to it's closer memory node, instead of
leaving it to OS.
mpool_sm_module.c:82: opal_maffinity_base_bind(&mseg, 1, mpool_sm->mem_n
Actually the size is suppose to be the same,
It just suppose to bind process to it's closer memory node, instead of
leaving it to OS.
see:
mpool_sm_module.c:82:opal_maffinity_base_bind(&mseg, 1,
mpool_sm->mem_node);
Best regards
Lenny.
On Mon, Jan 12, 2009 at 10:02 PM, Eugene Loh wrote
I'm trying to understand how much shared memory is allocated when
maffinity is on.
The sm BTL sets up a file that is mmapped into each local process's
address space so that the processes on a node can communicate via shared
memory.
Actually, when maffinity indicates that there are multiple "
