On Thu, 10 Jul 2008, Pavel Shamis (Pasha) wrote:
FYI the issue was resolved - https://svn.open-mpi.org/trac/ompi/ticket/1376
Indeed, no more IBCM error message displayed with r18878. Thank you !
--
Bogdan Costescu
IWR, University of Heidelberg, INF 368, D-69120 Heidelberg, Germany
Phone:
FYI the issue was resolved - https://svn.open-mpi.org/trac/ompi/ticket/1376
Regards,
Pasha
Bogdan Costescu wrote:
On Thu, 3 Jul 2008, Pavel Shamis (Pasha) wrote:
I had similar issue recently. It will be nice to have option to
disable/enable *CM via config flags.
Not sure if this is
Pasha -- do you want to open a ticket?
Done. https://svn.open-mpi.org/trac/ompi/ticket/1376
Pasha.
I added patch to the ticked, please review.
Pasha.
Jeff Squyres wrote:
Ok:
https://svn.open-mpi.org/trac/ompi/ticket/1375
I think any of us could do this -- it's pretty straightforward. No
guarantees on when I can get to it; my 1.3 list is already pretty long...
On Jul 3, 2008, at
I see the same issue on my Mellanox OFED 1.3. IBCM module is loaded but
is no such device in system.
Jeff, looks like some bug in IBCM stuff... (not ompi)
I think we should print the error only if ibcm was explicitly
selected by user. But from the cpc level it is no way to know
about
On Thu, 3 Jul 2008, Pavel Shamis (Pasha) wrote:
I had similar issue recently. It will be nice to have option to
disable/enable *CM via config flags.
Not sure if this is related... I am looking at using a nightly 1.3
snapshot and I get this type of error messages when running:
capturing in the bug is good enough for me at this point, thanks Jeff
Jeff Squyres wrote:
Ok:
https://svn.open-mpi.org/trac/ompi/ticket/1375
I think any of us could do this -- it's pretty straightforward. No
guarantees on when I can get to it; my 1.3 list is already pretty long...
On Jul
Ok:
https://svn.open-mpi.org/trac/ompi/ticket/1375
I think any of us could do this -- it's pretty straightforward. No
guarantees on when I can get to it; my 1.3 list is already pretty long...
No problem. I will take this one.
Pasha.
On Jul 3, 2008, at 6:20 AM, Pavel Shamis (Pasha)
Ok:
https://svn.open-mpi.org/trac/ompi/ticket/1375
I think any of us could do this -- it's pretty straightforward. No
guarantees on when I can get to it; my 1.3 list is already pretty
long...
On Jul 3, 2008, at 6:20 AM, Pavel Shamis (Pasha) wrote:
Jeff Squyres wrote:
Do you need
Jeff Squyres wrote:
Do you need configury to disable building ibcm / rdmacm support?
The more I think about it, the more I think that these would be good
features to have for v1.3...
I had similar issue recently. It will be nice to have option to
disable/enable *CM via config flags.
On Jul
Do you need configury to disable building ibcm / rdmacm support?
The more I think about it, the more I think that these would be good
features to have for v1.3...
On Jul 3, 2008, at 2:52 AM, Don Kerr wrote:
I did not think it was required but it hung me up when I built ompi
on one system
I did not think it was required but it hung me up when I built ompi on
one system which had the ibcm libraries and then ran on a system without
the ibcm libs. I had another issue on the system without ibcm libs which
prevented my building there but I will go down that path again. Thanks.
Jeff
That is the IBCM library for the IBCM CPC -- IB connection manager
stuff.
It's not *necessary*; you could use the OOB CPC if you want to.
That being said, OMPI currently builds support for it (and links it
in) if it finds the right headers and library files. We don't
currently have
It appears that the mca_btl_openib.so has a dependency on libibcm.so.
Is this necessary?
14 matches
Mail list logo
