Thanks for the advice Edgar. This appears to help but does not
eliminate the problem. This is what I observe (out of maybe 10 trials)
when using '-mca io romio314':
- no failures using 40 processes across 2 nodes (each node has 20 cores)
- no failures if using 'MPI_File_write_at'
- same type of
Hi,
I'm bit confused now.
When I supply ompi_info, it gives:
*[user@localhost openmpi-x86_64]$ ompi_info *
*[localhost.localdomain:11068] Error: Unable to get the current working
directory*
* Package: Open MPI root@3fecdf07461e Distribution*
*Open MPI: 2.1.1*
*
>From the output you supplied, it looks like you are running Open MPI v2.1.x.
Did you install Open MPI v2.1.x from source, and install it into the same
directory that you had previously installed Open MPI v2.0.x?
If so, the warnings you are seeing (not errors) are likely the fact that there
I think you're mixing a few versions there:
- You mention installing Open MPI v1.10
- But you say that running ompi_info shows MCA v2.1 (which probably means Open
MPI v2.1)
- And you say that running your code with MCA v2.0 (which probably means Open
MPI v2.0) works
You might want to
one more thing,
can you run
rpm -qf /usr/lib64/openmpi/lib/openmpi/mca_shmem_mmap.so
and make sure this comes from the openmpi rpm ?
if not, you can remove the openmpi rpm, rm -rf
/usr/lib64/openmpi/lib/openmpi and then re-install the rpm
Cheers,
Gilles
On Fri, Oct 13, 2017 at 10:49 PM, Gilles
Abhisek ... Gilles asked which program you re trying to run, and how it
was linked with OpenMPI
Also please realise that you do not HAVE to use the openmpi packages
provided by your linux distribution.
It is perfectly OK to download, compile and install another version.
On 13 October 2017 at
can you run ldd on your binary ?
i suspect it might not use the right Open MPI library
Cheers,
Gilles
On Fri, Oct 13, 2017 at 10:41 PM, abhisek Mondal wrote:
> Hello,
>
> I'm getting this following error:
> [localhost.localdomain:00307]
Hello,
I'm getting this following error:
* [localhost.localdomain:00307] mca_base_component_repository_open: shmem
"/usr/lib64/openmpi/lib/openmpi/mca_shmem_mmap" uses an MCA interface that
is not recognized (component MCA v2.0.0 != supported MCA v2.1.0) -- ignored*
*
Hi,
let's take one or two steps back.
which version of Open MPI did you use in order to build your program ?
what does "not working under MCA2.1" mean ?
link error ? unresolved symbols ? runtime crash ?
please detail your environment and post all relevant error messages
Cheers,
Gilles
On
Hi,
I have installed an openmpi using following command:
*yum install openmpi-1.10.0-10.el7*
When I put *ompi_info* command it shows me that it is using MCAv.2.1. Is
there any way I can use MCA2.0 ?
My program is not working under MCA2.1.
Please help me out here.
Thank you
--
Abhisek Mondal
Hi,
I have installed an openmpi using following command:
*yum install openmpi-1.10.0-10.el7*
When I put *ompi_info* command it shows me that it is using MCAv.2.1. Is
there any way I can use MCA2.0 ?
My program is not working under MCA2.1.
Please help me out here.
Thank you.
--
Abhisek
Hello,
TEJASWI k, on ven. 13 oct. 2017 14:44:53 +0530, wrote:
> Thanks I could get the linkspeed when i tried with root user.
> But is there no other way?
See Brice's answer :)
> And what is the reason behind this limitation?
Ask Linux people, not us :)
I can only guess that they are afraid
Thanks I could get the linkspeed when i tried with root user.
But is there no other way? And what is the reason behind this limitation?
Thanks & Regards,
Tejaswi K
On 13-Oct-2017 2:30 PM, "Samuel Thibault" wrote:
Hello,
TEJASWI k, on ven. 13 oct. 2017 14:23:00 +0530,
Hello,
TEJASWI k, on ven. 13 oct. 2017 14:23:00 +0530, wrote:
> All the other details I am able to query but linkspeed (pciObj->attr->
> bridge.upstream.pci.linkspeed) is always 0.
> Do I need to enable any other flag to get linkspeed or am I going wrong
> somewhere?
You need to run as root for
Hello
On Linux, the PCI linkspeed requires root privileges unfortunately
(except for the uplink above NVIDIA GPUs where we have another way to
find it).
The only way to workaround this is to dump the topology as XML as root
and then reload it at runtime (e.g. with HWLOC_XMLFILE) :/
Brice
Le
I am trying to traverse the topology using hwloc APIs starting from a PCI
device till Host Bridge
My code snippet:
unsigned long flags = HWLOC_TOPOLOGY_FLAG_IO_DEVICES |
HWLOC_TOPOLOGY_FLAG_IO_BRIDGES;
retval = hwloc_topology_init();
retval = hwloc_topology_set_flags(topology,
16 matches
Mail list logo