Can anyone set my expectations with their real world experiences
regarding building Open MPI on one release of Linux and running on another.
If I were to...
Build OMPI on Redhat 4, will it run on later releases of Redhat, e.g.
Redhat 5?
Build OMPI on Suse 9, will it run on later releases of Su
On May 22, 2008, at 4:30 PM, Dirk Eddelbuettel wrote:
Can you see if /dev/infiniband exists? If it does, the OpenFabrics
kernel drivers are running. If not, they aren't.
Negative -- I have no /dev/infiniband. So his test idea seems
feasible which is nice!
Good!
Do you have any informati
Commit r18481 seems to confuse gcc 4.2 ...
george.
../../../../latency_recv/ompi/mpi/c/scatter.c: In function
‘MPI_Scatter’:
../../../../latency_recv/ompi/mpi/c/scatter.c:128: warning: suggest
parentheses around && within ||
../../../../latency_recv/ompi/mpi/c/gather.c: In function ‘MPI_G
On Thu, May 22, 2008 at 04:19:05PM -0400, Jeff Squyres wrote:
> On May 22, 2008, at 4:07 PM, Dirk Eddelbuettel wrote:
>
> > Is there a test I could run for you?
>
> Can you see if /dev/infiniband exists? If it does, the OpenFabrics
> kernel drivers are running. If not, they aren't.
Negative
On May 22, 2008, at 4:07 PM, Dirk Eddelbuettel wrote:
Is there a test I could run for you?
Can you see if /dev/infiniband exists? If it does, the OpenFabrics
kernel drivers are running. If not, they aren't.
Also, if this test depends on the Debian kernel packages, then we're
back to squ
On Thu, May 22, 2008 at 03:45:36PM -0400, Jeff Squyres wrote:
> On May 22, 2008, at 3:42 PM, Dirk Eddelbuettel wrote:
>
> >> When you install binary OMPI (which pulls in libibverbs and all the
> >> rest), do you set the OpenFabrics kernel drivers to start upon boot?
> >> Or does the user have to d
On May 22, 2008, at 3:42 PM, Dirk Eddelbuettel wrote:
When you install binary OMPI (which pulls in libibverbs and all the
rest), do you set the OpenFabrics kernel drivers to start upon boot?
Or does the user have to do that manually?
I think so. To the best of my knowledge, we don't do anythin
On Thu, May 22, 2008 at 03:35:03PM -0400, Jeff Squyres wrote:
> Dirk / Debian guys --
>
> When you install binary OMPI (which pulls in libibverbs and all the
> rest), do you set the OpenFabrics kernel drivers to start upon boot?
> Or does the user have to do that manually?
I think so. To the
Dirk / Debian guys --
When you install binary OMPI (which pulls in libibverbs and all the
rest), do you set the OpenFabrics kernel drivers to start upon boot?
Or does the user have to do that manually?
I ask because of the check Pasha proposes: if the user has started the
OpenFabrics ker
1. Driver doesn't support the HCA - If I remember correct , RH40 by
default doesn't support ConnectX hca . The device_list will be empty.
It is very exotic case.
2. Driver version doesn't correspond with fw version
3. FW was broken
4. Driver was broken and failed to start - it is not very ex
Brian W. Barrett wrote:
With MX, it's one initialization call (mx_init), and it's not clear from
the errors it can return that you can differentiate between the two cases.
If you run mx_init() on a machine without the MX driver loaded or no NIC
detected by the driver, you get a specific error
Done; thanks.
On May 22, 2008, at 11:01 AM, Jon Mason wrote:
I know this is slightly premature, but if someone could update the
link
below to reflect that iWARP is now supported in OMPI it would be much
appreciated.
http://www.open-mpi.org/faq/?category=openfabrics#iwarp-support
Thanks,
Jo
On May 22, 2008, at 11:53 AM, Pavel Shamis (Pasha) wrote:
1. Driver doesn't support the HCA - If I remember correct , RH40 by
default doesn't support ConnectX hca . The device_list will be
empty. It is very exotic case.
2. Driver version doesn't correspond with fw version
3. FW was broken
4.
On Thu, May 22, 2008 at 06:53:38PM +0300, Pavel Shamis (Pasha) wrote:
> If user will decide to upgrade his ompi + libibverb rpm/deb package
> install , he will be need to do a lot of other "annoying" steps, like:
> source code download, installing all required *-dev.rpm , compilation.
No -- Run
I'm not sure I follow this logic -- can you explain more?
Sure
Why does this only apply to binary distribution? If libibverbs is
installed by default, then OMPI will still build the openib BTL (and
therefore warn if it's not used). Granted, some distros will only
install libibverbs if
I know there was some recent discussion about priority of components,
but I wanted to double check. I am trying to understand what priority =
0 means.
My assumption is the following:
priority >= 0 means the component is selectable
priority < 0 means the component is not selectable
I ask thi
On Thu, 22 May 2008, Terry Dontje wrote:
The major difference here is that libmyriexpress is not being included
in mainline Linux distributions. Specifically: if you can find/use
libmyriexpress, it's likely because you have that hardware. The same
*used* to be true for libibverbs, but is no lo
I know this is slightly premature, but if someone could update the link
below to reflect that iWARP is now supported in OMPI it would be much
appreciated.
http://www.open-mpi.org/faq/?category=openfabrics#iwarp-support
Thanks,
Jon
Ah. On Linux, --without-threads really doesn't gain you that much. The
default glibc is still thread safe, and there are only a couple small
parts of the code that use locks (like the OOB TCP). It's generally just
easier to leave threads enabled on Linux.
Brian
On Thu, 22 May 2008, Don Ker
Thanks Jeff. Thanks Brian.
I ran into this because I was specifically trying to configure with
"--disable-progress-threads --disable-mpi-threads" at which point I
figured, might as well turn off all threads so I added
"--without-threads" as well. But can't live without mpi_leave_pinned so
thr
Jeff Squyres wrote:
On May 22, 2008, at 6:50 AM, Terry Dontje wrote:
Brian and I chatted a bit about this off-list, and I think we're in
agreement now:
- do not change the default value or meaning of
btl_base_want_component_unsed.
- major point of confusion: the openib BTL is actually fair
On May 22, 2008, at 5:26 AM, Pavel Shamis (Pasha) wrote:
Ok, we will have own warning mechanism. But we still open question,
Will
we show (by default) error message in case
when libibverbs exists but it is no hca in the hca_list ?
I think we should show the error. The problem of libibverbs def
On May 22, 2008, at 6:50 AM, Terry Dontje wrote:
Brian and I chatted a bit about this off-list, and I think we're in
agreement now:
- do not change the default value or meaning of
btl_base_want_component_unsed.
- major point of confusion: the openib BTL is actually fairly unique
in that it can
Jeff Squyres wrote:
Brian and I chatted a bit about this off-list, and I think we're in
agreement now:
- do not change the default value or meaning of
btl_base_want_component_unsed.
- major point of confusion: the openib BTL is actually fairly unique
in that it can (and does) tell the di
Brian and I chatted a bit about this off-list, and I think we're in
agreement now:
- do not change the default value or meaning of
btl_base_want_component_unsed.
- major point of confusion: the openib BTL is actually fairly unique
in that it can (and does) tell the difference between "t
25 matches
Mail list logo