Sorry for the confusion; I was asking George which one wins. I'm not active in
the MX portion of the OMPI code base, so I don't know which one is better /
should be used.
On Jun 18, 2010, at 8:19 AM, guillaume ranquet wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hello,
>
> s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
sorry for the very long delay, I didn't understood you waited an answer
from my side on this. (the debate seemed to be between maintainers)
do not hesitate to bug me if I'm not answering after some days.
to answer shortly:
- -yes I've tested t
George --
Scott's patch was different than the one you applied. Apparently, his fixes
this user's problem (I don't know if Guillaume tested yours).
Which one wins?
On Jun 3, 2010, at 9:49 AM, Scott Atchley wrote:
> On Jun 3, 2010, at 8:54 AM, guillaume ranquet wrote:
>
> > granquet@bordepl
On Jun 3, 2010, at 8:54 AM, guillaume ranquet wrote:
> granquet@bordeplage-15 ~ $ mpirun --mca btl mx,openib,sm,self --mca pml
> ^cm --mca mpi_leave_pinned 0 ~/bwlat/mpi_helloworld
> [bordeplage-15.bordeaux.grid5000.fr:02707] Error in mx_init (error No MX
> device entry in /dev.)
> Hello world fro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/02/2010 07:51 PM, Jeff Squyres wrote:
>>From your prior mails:
>
> - there's no segv when ptmalloc is disabled at run-time via the env var
> - there's no segv when MX is completed disabled (both BTL and MTL)
>
> What happens if you run with onl
On Jun 2, 2010, at 1:31 PM, guillaume ranquet wrote:
> granquet@bordeplage-9 ~/openmpi-1.4.2 $ ~/openmpi-1.4.2-bin/bin/mpirun
> - --mca btl openib,sm,self --mca pml ^cm ~/bwlat/mpi_helloworld
> Hello world from process 0 of 1
> granquet@bordeplage-9 ~/openmpi-1.4.2 $
>
> I can tell it works :)
O
On Jun 2, 2010, at 1:51 PM, Jeff Squyres wrote:
>>> Ok, there is no segfault when it can't find IB.
>
> I'm not sure I follow this comment.
MX initialization is interfering on IB nodes (that do not have MX). I wanted to
make sure the opposite was not true (and it is not). :-)
Scott
On Jun 2, 2010, at 1:31 PM, guillaume ranquet wrote:
> > ~/openmpi-1.4.2-bin/bin/mpirun --mca btl openib,sm,self --mca pml ^cm
> > ~/bwlat/mpi_helloworld
>
> the first command seems to be wrong, I had an error message:
> MCA framework parameters can only take a single negation operator
Correct.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/02/2010 06:00 PM, Scott Atchley wrote:
> On Jun 2, 2010, at 11:52 AM, Scott Atchley wrote:
>
>> What if you explicitly disable MX?
>>
>> ~/openmpi-1.4.2-bin/bin/mpirun --mca btl openib,sm,self --mca btl ^mx
>> ~/bwlat/mpi_helloworld
>
> And ca
On Jun 2, 2010, at 11:52 AM, Scott Atchley wrote:
> What if you explicitly disable MX?
>
> ~/openmpi-1.4.2-bin/bin/mpirun --mca btl openib,sm,self --mca btl ^mx
> ~/bwlat/mpi_helloworld
And can you try this as well?
~/openmpi-1.4.2-bin/bin/mpirun --mca btl openib,sm,self --mca pml ^cm
~/bwlat
On Jun 2, 2010, at 11:14 AM, guillaume ranquet wrote:
>> What happens if you run:
>>
>> ~/openmpi-1.4.2-bin/bin/mpirun --mca btl openib,sm,self
>> ~/bwlat/mpi_helloworld
>>
>> (i.e., MX support is still compiled in, but remove MX from the run-time)
>
> sadly, exactly the same thing :(
> it doe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I snipped some parts of the exchange and responding to 2 mails in this
one. (this may not be proper netiquette on this ML?)
On 06/02/2010 03:54 PM, Jeff Squyres wrote:
> What happens if you run:
>
> ~/openmpi-1.4.2-bin/bin/mpirun --mca btl openib,sm,
On Jun 2, 2010, at 9:54 AM, Jeff Squyres wrote:
>> this is the output I get on a node with ethernet and infiniband hardware.
>> note the Error regarding mx.
>>
>> $ ~/openmpi-1.4.2-bin/bin/mpirun ~/bwlat/mpi_helloworld
>> [bordeplage-9.bordeaux.grid5000.fr:32365] Error in mx_init (error No MX
>>
On Jun 2, 2010, at 8:42 AM, guillaume ranquet wrote:
> yes, I have multiple clusters, some with infiniband, some with mx, some
> nodes with both Myrinet et Infiniband hardware and others with ethernet
> only.
>
> I reproduced it on a vanilla 1.4.1 and 1.4.2 with and without the
> - --with-mx swit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
yes, I have multiple clusters, some with infiniband, some with mx, some
nodes with both Myrinet et Infiniband hardware and others with ethernet
only.
I reproduced it on a vanilla 1.4.1 and 1.4.2 with and without the
- --with-mx switch.
this is t
Are you running on nodes with both MX and OpenFabrics?
I don't know if this is a well-tested scenario -- there may be some strange
interactions in the registered memory management between MX and OpenFabrics
verbs.
FWIW, you should be able to disable Open MPI's memory management at run time in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
we use a slightly modified openmpi-1.4.1
the patch is here:
- --- ompi/mca/btl/tcp/btl_tcp_proc.c.orig2010-03-23
14:01:28.0 +0100
+++ ompi/mca/btl/tcp/btl_tcp_proc.c 2010-03-23 14:01:50.0 +0100
@@ -496,7 +496,7 @@
What OMPI version are you using?
On May 31, 2010, at 5:37 AM, guillaume ranquet wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
> I'm new to the list and quite new to the world of MPI.
>
> a bit of background:
> I'm a sysadmin and have to provide a working environment (debian b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I'm new to the list and quite new to the world of MPI.
a bit of background:
I'm a sysadmin and have to provide a working environment (debian base)
for researchers to work with MPI : I'm _NOT_ an open-mpi user - I know
C, but that's all.
I compile
19 matches
Mail list logo
