<div dir="ltr">No, they are the same one. I mounted the directory to MICs by myself.</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, May 23, 2014 at 5:13 PM, Min Si <span dir="ltr"><<a href="mailto:msi@il.is.s.u-tokyo.ac.jp" target="_blank">msi@il.is.s.u-tokyo.ac.jp</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
Have you tried ssh to MIC and check mpiexec.hydra again ? It might
be different files just using the same path.<span class="HOEnZb"><font color="#888888"><br>
<br>
Min</font></span><div><div class="h5"><br>
<br>
<div>(14-5-23 15:48), Yida Wang wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">I don't know how Intel guys implement this. But I
think the mpiexec.hydra file they provide is a regular Linux
executable file. "file" it returns "mpiexec.hydra: ELF 64-bit
LSB executable, x86-64, version 1 (SYSV), dynamically linked
(uses shared libs), for GNU/Linux 2.6.9, not stripped".
<div>
<br>
</div>
<div>One need to make sure mpiexec.hydra and pmi_proxy are
accessible to MICs before launching processes on MICs from
host.</div>
</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">On Fri, May 23, 2014 at 4:43 PM, Reuti
<span dir="ltr"><<a href="mailto:reuti@staff.uni-marburg.de" target="_blank">reuti@staff.uni-marburg.de</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">
<div>
<div>Am 23.05.2014 um 22:38 schrieb Yida Wang:</div>
<div><br>
<blockquote type="cite">
<div dir="ltr">Thank you! That works, but is not
very convenient. Can I know why you guys don't
configure mpich to behave as the same as
Intel-MPI? Basically, using Intel-MPI, one can use
the same mpiexec.hydra on both host and Xeon Phi.</div>
</blockquote>
<div><br>
</div>
</div>
<div>I don't have Intel-MPI, but is it really a binary
or a wrapper to two different versions? What does
`file mpiexec.hydra` show?</div>
<span><font color="#888888">
<div>
<br>
</div>
<div>-- Reuti</div>
</font></span>
<div>
<div>
<div><br>
</div>
<br>
<blockquote type="cite">
<div class="gmail_extra">
<div class="gmail_quote">On Fri, May 23, 2014 at
1:18 PM, "Antonio J. Peña" <span dir="ltr"><<a href="mailto:apenya@mcs.anl.gov" target="_blank">apenya@mcs.anl.gov</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div><br>
For that, you have to deploy two
installations of MPICH: one compiled for
the host, and the other for the MIC. To
make things easy, place them under the
same path in both hosts - one that is
not shared.<br>
<br>
Antonio
<div>
<div><br>
<br>
<br>
On 05/22/2014 04:28 PM, Yida Wang
wrote:<br>
</div>
</div>
</div>
<blockquote type="cite">
<div>
<div>
<div dir="ltr">Hi Guys,
<div><br>
</div>
<div>Can MPICH be configured to
support launching processes on
Intel-MIC from the host? I know
that there's a way to compile
MPICH to be running on Intel-MIC
only, but how about running
heterogeneously on both host and
Intel-MIC together?</div>
<div><br>
</div>
<div>My compiled version returned
"hydra_pmi_proxy: cannot execute
binary file" and got stuck when
I tried to launch processes on
Intel-MIC.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>YW</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div>
</div>
<pre>_______________________________________________
discuss mailing list <a href="mailto:discuss@mpich.org" target="_blank">discuss@mpich.org</a>
To manage subscription options or unsubscribe:
<a href="https://lists.mpich.org/mailman/listinfo/discuss" target="_blank">https://lists.mpich.org/mailman/listinfo/discuss</a></pre>
<span><font color="#888888"> </font></span></blockquote>
<span><font color="#888888"> <br>
<br>
<pre cols="72">--
Antonio J. Peña
Postdoctoral Appointee
Mathematics and Computer Science Division
Argonne National Laboratory
9700 South Cass Avenue, Bldg. 240, Of. 3148
Argonne, IL 60439-4847
<a href="mailto:apenya@mcs.anl.gov" target="_blank">apenya@mcs.anl.gov</a>
<a href="http://www.mcs.anl.gov/%7Eapenya" target="_blank">www.mcs.anl.gov/~apenya</a></pre>
</font></span></div>
<br>
_______________________________________________<br>
discuss mailing list <a href="mailto:discuss@mpich.org" target="_blank">discuss@mpich.org</a><br>
To manage subscription options or
unsubscribe:<br>
<a href="https://lists.mpich.org/mailman/listinfo/discuss" target="_blank">https://lists.mpich.org/mailman/listinfo/discuss</a><br>
</blockquote>
</div>
<br>
</div>
_______________________________________________<br>
discuss mailing list <a href="mailto:discuss@mpich.org" target="_blank">discuss@mpich.org</a><br>
To manage subscription options or unsubscribe:<br>
<a href="https://lists.mpich.org/mailman/listinfo/discuss" target="_blank">https://lists.mpich.org/mailman/listinfo/discuss</a></blockquote>
</div>
</div>
</div>
<br>
</div>
<br>
_______________________________________________<br>
discuss mailing list <a href="mailto:discuss@mpich.org" target="_blank">discuss@mpich.org</a><br>
To manage subscription options or unsubscribe:<br>
<a href="https://lists.mpich.org/mailman/listinfo/discuss" target="_blank">https://lists.mpich.org/mailman/listinfo/discuss</a><br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
discuss mailing list <a href="mailto:discuss@mpich.org" target="_blank">discuss@mpich.org</a>
To manage subscription options or unsubscribe:
<a href="https://lists.mpich.org/mailman/listinfo/discuss" target="_blank">https://lists.mpich.org/mailman/listinfo/discuss</a></pre>
</blockquote>
<br>
</div></div></div>
<br>_______________________________________________<br>
discuss mailing list <a href="mailto:discuss@mpich.org">discuss@mpich.org</a><br>
To manage subscription options or unsubscribe:<br>
<a href="https://lists.mpich.org/mailman/listinfo/discuss" target="_blank">https://lists.mpich.org/mailman/listinfo/discuss</a><br></blockquote></div><br></div>