Hi Pavan,

Thanks for letting me know. One follow-up (maybe silly) question, how can I pick tcp at runtime instead of scif?

Yida

On Mon, May 26, 2014 at 3:06 PM, Balaji, Pavan <balaji@anl.gov> wrote:

Hi Yida,

Using SCIF + TCP (+ shared memory, which is implicit) together within the same job is not supported right now.  When you configure with scif,tcp, you can pick either one at runtime, but not both.

We are working on some improvements to this for the next major release (3.2).  Please stay tuned.

Regards,

  — Pavan

On May 26, 2014, at 10:50 AM, Yida Wang <yidawa@gmail.com> wrote:

> Hi Guys,
>
> During configuration, I put in an optional argument as "--with-device=ch3:nemesis:scif,tcp" to hopefully enable scif communication through PCIe, and use tcp for remote communication.
>
> However, it looks like that tcp channel is disabled by this setting. That is, when I wanted to communicate between remote Xeon Phis, it returned error saying that "channel initialization failed" and "scif_connect failed", where I assume that tcp channel should be used instead of scif.
>
> Moreover, when communicating between two remote hosts, it would get stuck probably because it still tried to use scif channel.
>
> Did I configure the communication device incorrectly?
>
> Thanks,
> YW

> _______________________________________________
> discuss mailing list     discuss@mpich.org
> To manage subscription options or unsubscribe:
> https://lists.mpich.org/mailman/listinfo/discuss

_______________________________________________
discuss mailing list     discuss@mpich.org
To manage subscription options or unsubscribe:
https://lists.mpich.org/mailman/listinfo/discuss