RE: some dapl assistance - [PATCH] dapl-2.0 improperly handles pkeycheck/query in host order

2010-07-20 Thread Itay Berman
. -Original Message- From: Davis, Arlin R [mailto:arlin.r.da...@intel.com] Sent: ב 19 יולי 2010 22:04 To: Itay Berman Cc: linux-rdma; Or Gerlitz Subject: RE: some dapl assistance - [PATCH] dapl-2.0 improperly handles pkeycheck/query in host order Itay, OK, we got Intel MPI to run. To test

RE: some dapl assistance - [PATCH] dapl-2.0 improperly handles pkey check/query in host order

2010-07-19 Thread Davis, Arlin R
Itay, OK, we got Intel MPI to run. To test the pkey usage we configured it to run over pkey that is not configured on the node. In this case the MPI should have failed, but it didn't. The dapl debug reports the given pkey (0x8001 = 32769). How can that be? If the pkey override is not valid

RE: some dapl assistance

2010-07-15 Thread Itay Berman
...@voltaire.com] Sent: Tuesday, July 13, 2010 4:41 AM To: Davis, Arlin R Cc: Itay Berman; linux-rdma Subject: Re: some dapl assistance Davis, Arlin R wrote: There is limited debug in the non-debug builds. If you want full debugging capabilities you can install the source RPM and configure and make

RE: some dapl assistance

2010-07-15 Thread Davis, Arlin R
OK, we got Intel MPI to run. To test the pkey usage we configured it to run over pkey that is not configured on the node. In this case the MPI should have failed, but it didn't. The dapl debug reports the given pkey (0x8001 = 32769). How can that be? Itay, If the pkey override is not valid

RE: some dapl assistance

2010-07-15 Thread Itay Berman
To: Itay Berman; Or Gerlitz Cc: linux-rdma Subject: RE: some dapl assistance OK, we got Intel MPI to run. To test the pkey usage we configured it to run over pkey that is not configured on the node. In this case the MPI should have failed, but it didn't. The dapl debug reports the given pkey (0x8001

RE: some dapl assistance

2010-07-15 Thread Davis, Arlin R
No: No. Same warning: dodly4:625b: Warning: new pkey(32770), query (Success) err or key !found, using defaults dodly4:625b: query_hca: port.link_layer = 0x1 dodly4:625b: query_hca: (a0.0) eps 262076, sz 16351 evds 65408, sz 4194303 mtu 2048 - pkey 32770 p_idx 0 sl 0 [r...@dodly0

RE: some dapl assistance

2010-07-15 Thread Davis, Arlin R
[mailto:it...@voltaire.com] Sent: Thursday, July 15, 2010 10:19 AM To: Davis, Arlin R; Or Gerlitz Cc: linux-rdma Subject: RE: some dapl assistance No: No. Same warning: [r...@dodly0 compat-dapl-1.2.18]# mpiexec -ppn 1 -n 2 -env I_MPI_FABRICS dapl:dapl -env I_MPI_DEBUG 2 -env

Re: some dapl assistance

2010-07-13 Thread Or Gerlitz
Davis, Arlin R wrote: There is limited debug in the non-debug builds. If you want full debugging capabilities you can install the source RPM and configure and make as follows [..] (OFED target example): okay, got that, once I built the sources by hand as you suggested I could see debug

RE: some dapl assistance

2010-07-13 Thread Davis, Arlin R
: Tuesday, July 13, 2010 4:41 AM To: Davis, Arlin R Cc: Itay Berman; linux-rdma Subject: Re: some dapl assistance Davis, Arlin R wrote: There is limited debug in the non-debug builds. If you want full debugging capabilities you can install the source RPM and configure and make as follows

RE: some dapl assistance

2010-07-07 Thread Davis, Arlin R
Or, What needs to be done such that the dapl debug prints be seen either in the system log or the standard output/error of the mpi rank? There is limited debug in the non-debug builds. If you want full debugging capabilities you can install the source RPM and configure and make as follow