[mpich-discuss] Can ch3:nemesis:mx use both MX and TCP networks ?
Darius Buntinas
buntinas at mcs.anl.gov
Wed Oct 14 10:51:14 CDT 2009
Martin,
How critical is this feature for you?
-d
On 10/13/2009 11:00 AM, Audet, Martin wrote:
> MPI_Users/MPI_Developers,
>
>
>
> I always thought (but never tested) that the ch3:nemesis:mx channel has
> the ability to independently select either MX or TCP to communicate
> between any pair of MPI processes when shared memory communication isn’t
> possible (e.g. the two process run on different nodes).
>
>
>
> However after carefully reading the README file, I fear mpich2 doesn’t
> have this flexibility that is, network communication with the
> ch3:nemesis:mx channel is always done using MX (of course network
> communication occurs when shared memory communication isn’t possible).
>
>
>
> Can someone clarify this ?
>
>
>
> When shared memory communication isn’t possible, does the ch3:nemesis:mx
> channel has the ability to independently select either MX or TCP to
> communicate between two MPI processes ?
>
>
>
> Thanks,
>
>
>
> Martin
>
More information about the mpich-discuss
mailing list