Le 25/08/2015 05:59, Christopher Samuel a écrit :
>
> INRIA does have Open-MX (Myrinet Express over Generic Ethernet
> Hardware), last release December 2014. No idea if it's still developed
> or used..
>
> http://open-mx.gforge.inria.fr/
>
> Brice?
>
> Open-MPI is listed as working with it there.
On 25/08/15 05:08, Jeff Squyres (jsquyres) wrote:
> FWIW, we have had verbal agreement in the past that the v1.8 series
> was the last one to contain MX support. I think it would be fine for
> all MX-related components to disappear from v1.10.
>
> Don't forget that Myricom as an HPC company no l
+1
On Mon, Aug 24, 2015 at 07:08:02PM +, Jeff Squyres (jsquyres) wrote:
> FWIW, we have had verbal agreement in the past that the v1.8 series was the
> last one to contain MX support. I think it would be fine for all MX-related
> components to disappear from v1.10.
>
> Don't forget that M
FWIW, we have had verbal agreement in the past that the v1.8 series was the
last one to contain MX support. I think it would be fine for all MX-related
components to disappear from v1.10.
Don't forget that Myricom as an HPC company no longer exists.
> On Aug 24, 2015, at 2:34 PM, Paul Hargrov
On Mon, Aug 24, 2015 at 10:52 AM, Paul Hargrove wrote:
> Thus if this newly reported problem is (as I am going to guess)
> in config/ompi_check_mx.m4 then it may go unfixed.
> You say you and I are the only ones to care, and I think we both care for
> reasons related to software quality rather th
Ah, my bad - thanks for correcting me!
I’ll have to ask folks tomorrow if we care about Myricom at this point.
> On Aug 24, 2015, at 10:52 AM, Paul Hargrove wrote:
>
> Ralph
>
> mx = Myricom (not Mellanox, which is mxm).
> So, there is probably nobody to fix anything specific to the MX suppo
Ralph
mx = Myricom (not Mellanox, which is mxm).
So, there is probably nobody to fix anything specific to the MX support.
Thus if this newly reported problem is (as I am going to guess)
in config/ompi_check_mx.m4 then it may go unfixed.
You say you and I are the only ones to care, and I think we
You know, if it wren’t for the impact it would have on our users, I’d almost
say that if Mellanox doesn’t care enough to ensure this works, then maybe we
should just release and see if someone actually does care?
I’ll try again later today if/when I have time. Otherwise, I’ll raise it at
tomorr
Sorry to yet again be the bearer of bad news.
I am now configuring with
--prefix=[...] --enable-debug --with-libfabric=/opt/libfabric-1.0.0
--with-mx=/opt/mx2g --disable-dlopen
This is like the previous configuration that caused problems, but with
"--disable-dlopen" instead of "--enable-static -
