> On 23 Nov 2020, at 13:50, Christopher Lameter <cl@xxxxxxxxx> wrote: > > On Sun, 22 Nov 2020, Christopher Lameter wrote: > >>> If you set acme_plus_kernel_only to one in said config file, you app will resolve the address using the kernel neighbour cache and the route resolution will go into the kernel and then "bounce" back to user space and ibacm through NetLink. >> >> Have not seen that in the RHEL7.8 version of ibacm. >> > > Got version 33.0 from Redhat with the option. Set it but ibacm still times > out when trying to contact the SM. Contact the peer ibacm, that is. Is it started? And, ib_acme bypasses the kernel_only check. I assume a real app (e.g., qperf <destination_ip> -cm1 rc_bw) would work, but incur an excess delay due to the ibacm timeout, before failing back to the kernel neighbour cache. Thxs, Håkon > > ib_acme says: > > ib_acm_resolve_ip failed: Connection timed out > > > ibmacm.log says > > acmp_process_wait_queue: notice - failing request > acmp_process_timeouts: notice - dest 192.168.50.39 > >
