From: Bart Van Assche <bvanassche@acm.org>
To: "Doug Ledford" <dledford@redhat.com>,
"Håkon Bugge" <haakon.bugge@oracle.com>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
"Leon Romanovsky" <leon@kernel.org>,
"Parav Pandit" <parav@mellanox.com>,
"Steve Wise" <swise@opengridcomputing.com>
Cc: linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] RDMA/cma: Make CM response timeout and # CM retries configurable
Date: Thu, 13 Jun 2019 08:28:53 -0700 [thread overview]
Message-ID: <2c114313-01fe-6d4d-5134-592d1a7b829b@acm.org> (raw)
In-Reply-To: <174ccd37a9ffa05d0c7c03fe80ff7170a9270824.camel@redhat.com>
On 6/13/19 7:25 AM, Doug Ledford wrote:
> So, to revive this patch, what I'd like to see is some attempt to
> actually quantify a reasonable timeout for the default backlog depth,
> then the patch should actually change the default to that reasonable
> timeout, and then put in the ability to adjust the timeout with some
> sort of doc guidance on how to calculate a reasonable timeout based on
> configured backlog depth.
How about following the approach of the SRP initiator driver? It derives
the CM timeout from the subnet manager timeout. The assumption behind
this is that in large networks the subnet manager timeout has to be set
higher than its default to make communication work. See also
srp_get_subnet_timeout().
Bart.
next prev parent reply other threads:[~2019-06-13 15:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 7:57 Håkon Bugge
2019-06-13 14:25 ` Doug Ledford
2019-06-13 15:28 ` Bart Van Assche [this message]
2019-06-13 16:32 ` Doug Ledford
2019-06-13 16:58 ` Håkon Bugge
2019-06-13 17:23 ` Jason Gunthorpe
2019-06-13 17:39 ` Håkon Bugge
2019-06-13 23:46 ` Jason Gunthorpe
2019-06-13 20:25 ` Doug Ledford
2019-06-14 5:44 ` Håkon Bugge
2019-10-29 12:59 ` Dag Moxnes
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=2c114313-01fe-6d4d-5134-592d1a7b829b@acm.org \
--to=bvanassche@acm.org \
--cc=dledford@redhat.com \
--cc=haakon.bugge@oracle.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=parav@mellanox.com \
--cc=swise@opengridcomputing.com \
/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
all inboxes | Powered by JetHome®