All of lore.kernel.org
 help / color / mirror / Atom feed
From: Or Gerlitz <ogerlitz-smomgflXvOZWk0Htik3J/w@public.gmane.org>
To: Mike Mundy <mmundy42-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, "Hefty,
	Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: rdma_listen() backlog maximum
Date: Sun, 6 Feb 2011 10:51:30 +0200	[thread overview]
Message-ID: <4D4E6112.4060008@voltaire.com> (raw)
In-Reply-To: <AANLkTikqiahK1qNc6_wS6X445oUoVUJsE-nd3uC-sPWs-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Mike Mundy wrote:
> I'm prototyping a server that needs to accept a large number of
> simultaneous incoming RDMA CM connections. I noticed that
> drivers/infiniband/core/ucma.c limits the backlog to 128. Is there a
> reason why the limit is 128? Or to put it another way, what breaks if
> the limit is increased to a larger value (say 256)?

My understanding is that with the current cma/cm code, under IB/IBoE
the backlog has no impact, in that environment, you're practically 
limited by the mad layer ability to receive the REQ mads. Sean, am I 
correct?

Or.
--
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

  parent reply	other threads:[~2011-02-06  8:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-03 16:40 rdma_listen() backlog maximum Mike Mundy
     [not found] ` <AANLkTikqiahK1qNc6_wS6X445oUoVUJsE-nd3uC-sPWs-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-02-03 17:26   ` Roland Dreier
2011-02-06  8:51   ` Or Gerlitz [this message]
     [not found]     ` <4D4E6112.4060008-smomgflXvOZWk0Htik3J/w@public.gmane.org>
2011-02-07 17:54       ` Hefty, Sean
     [not found]         ` <CF9C39F99A89134C9CF9C4CCB68B8DDF25CC26962E-osO9UTpF0USkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2011-02-08  3:51           ` Or Gerlitz

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=4D4E6112.4060008@voltaire.com \
    --to=ogerlitz-smomgflxvozwk0htik3j/w@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mmundy42-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.