Jason, I am down to two errors and about 30 skips in run_test.py. device_ex, cq_ex and qp_ex verbs are working. The two errors are from the same source and occur for async multicast rdmacm. The immediate cause of the problem is the test harness is setting up an IPv4 multicast address and then two end points start sending traffic to that address. These packets are delivered to the driver and received by rxe_rcv which tries to resolve a gid table entry for them and fails. The unicast IPv4 address is 192.168.0.21 which does have a gid table entry. The multicast address is 230.168.0.21 which does not. Presumably the driver wants the gid table entry so it can use it to provide a source address for return traffic but that would just be the unicast address I think. The network stack knows which interface the traffic was received on but rdma/core is trying to solve the problem with just the IP address and doesn't seem to recognize it as a multicast address or have any clever idea what to do besides searching the gid table. This seems to be a rdma/core issue more than a rxe issue. But it must have come up in the past somewhere. BTW I got around the other addressing problem I was having by just adding the eui48 IPV5 address by hand with ip addr add. Bob
