On Thu, Jul 22, 2010 at 3:15 AM, Or Gerlitz <ogerl...@voltaire.com> wrote: > Hari Subramoni wrote: >> [subra...@amd6 perftest]$ ./ib_rdma_bw -c 172.16.1.5 >> 11928: | port=18515 | ib_port=1 | size=65536 | tx_depth=100 | iters=1000 | >> duplex=0 | cma=1 | >> 11928: Local address: LID 0000, QPN 000000, PSN 0x5bfbba RKey 0x90042602 >> VAddr 0x002b27feabe000 >> 11928: Remote address: LID 0000, QPN 000000, PSN 0x392fe6, RKey 0xf8042605 >> VAddr 0x002b9d5c93b000 > > > you can see the lid and qp numbers are zero, something is broken... when you > use the rdma-cm, > the address to be provided to the utility should be on an IPoIB subnet, is > that what you're doing? > > Basically, I would suggest that you first use rping(1) provided by > librdmacm-utils to make > sure things are working well in your configuration and then move to the > perftest utils.
Thanks for the response Or. I'm posting some information below. Here is the output I get when running rping... [perki...@amd5 ~]$ rping -v -s -a 172.16.1.5 [perki...@amd6 ~]$ rping -v -c -a 172.16.1.5 cq completion failed status 5 cma event RDMA_CM_EVENT_REJECTED, error 8 wait for CONNECTED state 10 connect error -1 [perki...@amd6 ~]$ ping 172.16.1.5 PING 172.16.1.5 (172.16.1.5) 56(84) bytes of data. 64 bytes from 172.16.1.5: icmp_seq=1 ttl=64 time=3.45 ms 64 bytes from 172.16.1.5: icmp_seq=2 ttl=64 time=1.00 ms We are able to ping the addresses but you can see that rping results in a failure. We have two interfaces exposed on each machine both on different subnets (172.16.1.0/24 and 172.16.2.0/24). We're using ofed-1.5.1 on these systems. Any idea of what could be going on? -- Jonathan Perkins -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
