public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Arun Kaimalettu <arun.kaimalettu-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: slow rdma_connect
Date: Thu, 11 Aug 2011 22:16:20 +0530	[thread overview]
Message-ID: <4E44075C.2@oracle.com> (raw)

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

             reply	other threads:[~2011-08-11 16:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-11 16:46 Arun Kaimalettu [this message]
     [not found] ` <4E44075C.2-QHcLZuEGTsvQT0dZR+AlfA@public.gmane.org>
2011-08-11 17:19   ` slow rdma_connect Hefty, Sean

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4E44075C.2@oracle.com \
    --to=arun.kaimalettu-qhclzuegtsvqt0dzr+alfa@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox