public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
* slow rdma_connect
@ 2011-08-11 16:46 Arun Kaimalettu
       [not found] ` <4E44075C.2-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
  0 siblings, 1 reply; 2+ messages in thread
From: Arun Kaimalettu @ 2011-08-11 16:46 UTC (permalink / raw)
  To: linux-rdma-u79uwXL29TY76Z2rM5mHXA

Hi,

We have a client-sever application that use rdma cm to establish connections
to do RDMA.   It takes around 30 or 40 secs for 500 clients started 
simultaneously
to complete the connections to a server.  The machine where we are testing
has enough CPU resource , so this 30 - 40secs appears to be the time for
rdma_cm to transition from resolving address to establishing connections..
Is this expected or should we be configuring rdma cm to handle this load ?

set of system calls involved in both sides are:

server:
rdma_create_id, rdma_listen, loop with { select, rdma_get_cm_event}
(listen backlog is 10)

client:
rdma_create_id, rdma_resolve_addr, rdma_resolve_route, rdma_connect, 
loop with { select rdma_get_cm_event}
(resolve timeouts are 20ms,
connect parameters are :
   param.responder_resources = 1;
   param.initiator_depth     = 1;
   param.rnr_retry_count     = 7;
   param.retry_count         = 7;
}

versions:
libibcm-1.0.5-1
ibacm-1.0.3-1
librdmacm-1.0.13-1

--
thanks,
arun

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

^ permalink raw reply	[flat|nested] 2+ messages in thread

* RE: slow rdma_connect
       [not found] ` <4E44075C.2-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
@ 2011-08-11 17:19   ` Hefty, Sean
  0 siblings, 0 replies; 2+ messages in thread
From: Hefty, Sean @ 2011-08-11 17:19 UTC (permalink / raw)
  To: Arun Kaimalettu,
	linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org

> to complete the connections to a server.  The machine where we are testing
> has enough CPU resource , so this 30 - 40secs appears to be the time for
> rdma_cm to transition from resolving address to establishing connections..
> Is this expected or should we be configuring rdma cm to handle this load ?

The rdma_cm can handle this load, but...
 
> set of system calls involved in both sides are:
> 
> server:
> rdma_create_id, rdma_listen, loop with { select, rdma_get_cm_event}
> (listen backlog is 10)

the backlog is the issue.  With a backlog of only 10, all additional incoming requests get dropped and must be retried.  The connect retry is a couple of seconds.  Try increasing the backlog (or setting it to 0).

- Sean
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2011-08-11 17:19 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-08-11 16:46 slow rdma_connect Arun Kaimalettu
     [not found] ` <4E44075C.2-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2011-08-11 17:19   ` Hefty, Sean

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox