>Oddly enough, I'm back to the same problem with your new patch as I saw >with the unpatched version: Hmmm. We ran this with OFED 1.1 RC3 and MPI 3.0b on an EM64T server with your adapter and it worked.
Did you ever pick up the Intel MPI 3.0 beta? > > $ mpiexec -n 2 ./a.out > I_MPI: [1] MPIDI_CH3I_RDMA_init(): will use DAPL provider from >registry: OpenIB-cma > I_MPI: [0] MPIDI_CH3I_RDMA_init(): will use DAPL provider from >registry: OpenIB-cma > I_MPI: [0] MPIDI_CH3_Init(): I_MPI: [1] MPIDI_CH3_Init(): will use >rdma configuration > will use rdma configuration > [1:ib-idev-06][rdma_iba_init_d.c:154] error(0x60029): OpenIB-cma: >could not create DAPL endpoint: DAT_INVALID_PARAMETER(DAT_INVALID_ARG6) > Hello world: rank 0 of 2 running on ib-idev-05 > rank 1 in job 1 ib-idev-05_51891 caused collective abort of all ranks > exit status of rank 1: killed by signal 9 > >Still tracking this one down. I noticed in the patch you removed a >couple of lines, too: > > - ia_attr->max_rdma_read_per_ep = dev_attr.max_qp_rd_atom; > >Any particular reason why you did this? max_rdma_read_per_ep is the same as max_rdma_read_per_ep_in. Look at dat.h line #369 /* To support backwards compatibility for DAPL-1.0 */ #define max_rdma_read_per_ep max_rdma_read_per_ep_in #define DAT_IA_FIELD_IA_MAX_DTO_PER_OP DAT_IA_FIELD_IA_MAX_DTO_PER_EP_IN /* To support backwards compatibility for DAPL-1.0 & DAPL-1.1 */ #define max_mtu_size max_message_size -arlin _______________________________________________ openib-general mailing list openib-general@openib.org http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general