Enabling/disabling Myrinet shared memory with mpiexec

Chris Samuel csamuel at vpac.org
Thu Mar 31 21:05:39 EST 2005


On Fri, 1 Apr 2005 11:22 am, Chris Samuel wrote:

> but as it and GMPI_SHEMEM_PREFIX are never set in the first place I can't
> see how it that would make any difference ?

The file referenced by GMPI_SHMEM_PREFIX is explained here:

	http://www.myri.com/fom-serve/cache/265.html

It says:

	The shared memory file is a file in /tmp (with a name like
	gmpi_shmem-<magic>:0.tmp where <magic> is the magic number of the job) that
	all local processes open and mmap() to create a shared memory segment.

So my guess is that if that variable isn't set then Myrinet shmem stuff won't 
work (not that it's always desirable according to that previous FAQ!).

Chris
-- 
 Christopher Samuel - (03)9925 4751 - VPAC Deputy Systems Manager
 Victorian Partnership for Advanced Computing http://www.vpac.org/
 Bldg 91, 110 Victoria Street, Carlton South, VIC 3053, Australia

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://email.osc.edu/pipermail/mpiexec/attachments/20050401/68443262/attachment.bin


More information about the mpiexec mailing list