I very much doubt that either of those mappers has ever been tested against
comm_spawn. Just glancing thru them, I don't see an immediate reason why
loadbalance wouldn't work, but the error indicates that the system wound up
mapping one or more processes to an unknown node.
We are revising the
All of the hosts that will be used in the job must be included in the original
hostfile - even if the hosts won't be used until comm_spawn.
The name in the hostfile must match the name provided in the info object as we
otherwise would have to do DNS resolves to detect the alias, which would have
Oups, sorry !
I followed these steps :
1) Install a debian system (sarge 3.1r2).
2) Use a 2.6.9 kernel patched with bproc 4.0.0pre8
(http://bproc.sourceforge.net)
the options CONFIG_BPROC, CONFIG_ROMFS_FS, CONFIG_BLK_DEV_RAM,
CONFIG_BLK_DEV_INITRD, CONFIG_TMPFS where activated via the 'make me
Could you please clarify - what "Bproc kernel patch" are you referring to?
Thanks
Ralph
On 9/27/06 2:37 AM, "laurent.po...@fr.thalesgroup.com"
wrote:
> Hi,
>
> I'm using MPI_Comm_spawn_multiple with Open MPI 1.1.1.
> It used to work well, until I used the Bproc kernel patch.
>
> When I use
