[ofw] problem about rdma_bw

Hefty, Sean sean.hefty at intel.com
Wed Jul 21 10:40:39 PDT 2010


copying ofw mail list

> Ethernet adapter Local Area Connection:
>    Connection-specific DNS Suffix  . : vis08.loc
>    Description . . . . . . . . . . . : OpenFabrics IPoIB Adapter
>    Physical Address. . . . . . . . . : 00-06-6A-FF-11-8C
>    DHCP Enabled. . . . . . . . . . . : Yes
>    Autoconfiguration Enabled . . . . : Yes
>    Link-local IPv6 Address . . . . . :
> fe80::f08b:ccc6:2d5d:6c3d%29(Preferred)
>    IPv4 Address. . . . . . . . . . . : 192.168.2.125(Preferred)
>    Subnet Mask . . . . . . . . . . . : 255.255.255.0
>    Lease Obtained. . . . . . . . . . : Dienstag, 20. Juli 2010 10:34:06
>    Lease Expires . . . . . . . . . . : Mittwoch, 28. Juli 2010 10:34:06
>    Default Gateway . . . . . . . . . : 0.0.0.0
>    DHCP Server . . . . . . . . . . . : 192.168.2.141
>    DHCPv6 IAID . . . . . . . . . . . : 486540906
>    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-4F-97-EF-00-30-48-56-
> 20-BB
>    DNS Servers . . . . . . . . . . . : 192.168.0.11
>                          141.58.1.1
>    NetBIOS over Tcpip. . . . . . . . : Enabled
> The problem is as follows:
> In its README.txt document, it contains two situations:
> (1)  server:    ibv_rdma_bw
> client:    ibv_rdma_bw -h <ethernet-hostname>
> For this one, I open two different cmd windows to test using the following
> commands:
> server:  ibv_rdma_bw
> client:  ibv_rdma_bw –h 192.168.2.125
> And it can work.
> (2) server:    ibv_rdma_bw -c
> client:    ibv_rdma_bw -c -h IPoIB-IF-IPv4-address
> For this case, I use the following commands:
> server:  ibv_rdma_bw –c
> It returns the error: rdma_bind_addr failed.
> client:  ibv_rdma_bw –c –h 192.168.2.125
> It returns the error: rdma_resolve_addr failed.
> Do you have some ideas what is wrong here?

I just ran a test on my system, and the -c option worked okay.  Looking at your configuration, I don't see anything standing out as an issue.  If you run rdma_cmatose without any options, does that fail for you as well?  Can you also try adding -p port_number to the command line?  Maybe there's a port collision for some reason.

- Sean


More information about the ofw mailing list