Hi,
I think, on the contrary, that he did notice the AMD/ARM issue. I suppose
you haven't read the text (and I like the fact that there are different
opinions on this issue).
Matthieu
2018-01-05 8:23 GMT+01:00 Gilles Gouaillardet :
> John,
>
>
> The technical assessment so to speak is linked in
I believe this snippet sums it up pretty well:
"Now you have a bit more context about why Intel’s response was, well, a
non-response. They blamed others, correctly, for having the same problem
but their blanket statement avoided the obvious issue of the others aren’t
crippled by the effects of the
Hello All,
Please people, just drop it. I appreciated the initial post in
response to to the valid question of how these bugs might impact OMPI
and message passing in general. At this point, y'all are beating the
proverbial dead horse. If you wish to debate, please mail each other
directl
That is enough, folks. This is an email forum for users to get help regarding
Open MPI, not a place to vent your feelings about specific vendors. We ask that
you respect that policy and refrain from engaging in such behavior.
We don’t care if you are quoting someone else - the fact that “Mikey s
An article with "market share" in the title is not a technical assessment,
but in any case, you aren't willing to respect the request to focus on
Open-MPI on the Open-MPI list, so I'll be piping mail from your address to
trash from now on.
Jeff
On Thu, Jan 4, 2018 at 10:54 PM, John Chludzinski <
I am attempting to install openmpi-1.10.7 on CentOS Linux (7.4.1708) using
GCC-6.4.0.
When compiling, I get the following error:
make[2]: Leaving directory '/home/vaskarpo/bin/openmpi-1.10.7/ompi/mca/pml/ob1'
Making all in mca/pml/ucx
make[2]: Entering directory '/home/vaskarpo/bin/openmpi-1.10
I forget what the underlying issue was, but this issue just came up and was
recently fixed:
https://github.com/open-mpi/ompi/issues/4345
However, the v1.10 series is fairly ancient -- the fix was not applied to that
series. The fix was applied to the v2.1.x series, and a snapshot tarball
Thank you Jeff for your suggestion to use the v.2.1 series.
I am attempting to use openmpi with EPW. On the EPW website
(http://epw.org.uk/Main/DownloadAndInstall), it is stated that:
Compatibility of EPW
EPW is tested and should work on the following compilers and libraries:
* gcc640 ser
You can still give Open MPI 2.1.1 a try. It should be source compatible with
EPW. Hopefully the behavior is close enough that it should work.
If not, please encourage the EPW developers to upgrade. v3.0.x is the current
stable series; v1.10.x is ancient.
> On Jan 5, 2018, at 5:22 PM, Vahid
Vahid,
This looks like the description of the issue reported at
https://github.com/open-mpi/ompi/issues/4336
The fix is currently available in 3.0.1rc1, and I will back port the fix fo
the v2.x branch.
A workaround is to use ROM-IO instead of ompio, you can achieve this with
mpirun —mca io ^ompio
Gilles,
I will try the 3.0.1rc1 version to see how it goes.
Thanks,
Vahid
On Jan 5, 2018, at 8:40 PM, Gilles Gouaillardet
mailto:gilles.gouaillar...@gmail.com>> wrote:
Vahid,
This looks like the description of the issue reported at
https://github.com/open-mpi/ompi/issues/4336
The fix is cu
11 matches
Mail list logo
