From: Jason Gunthorpe <jgg@nvidia.com>
To: Haakon Bugge <haakon.bugge@oracle.com>
Cc: Parav Pandit <parav@nvidia.com>,
Doug Ledford <dledford@redhat.com>,
OFED mailing list <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH for-next] IB/cma: Introduce rdma_set_min_rnr_timer()
Date: Wed, 31 Mar 2021 14:50:06 -0300 [thread overview]
Message-ID: <20210331175006.GQ1463678@nvidia.com> (raw)
In-Reply-To: <C55F49E9-900D-43F5-9430-E62249B801E4@oracle.com>
On Wed, Mar 31, 2021 at 05:45:30PM +0000, Haakon Bugge wrote:
> True. Local ACK Timeout is part of CM REQ. But that makes
> 2c1619edef61 ("IB/cma: Define option to set ack timeout and pack
> tos_set") fuzzy, as it claims in the commentary: "The timeout will
> affect the local side of the QP, it is not negotiated with remote
> side ..."
Hmm, is it intended to replace the CM provided local ack timeout on
the responder side?
It doesn't look like it copied into the MAD though, and the
qp_attr->timeout only looks like it is et for the IB_QPT_XRC_TGT case??
Very confusing indeed. Parav?
Jason
next prev parent reply other threads:[~2021-03-31 17:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 13:05 [PATCH for-next] IB/cma: Introduce rdma_set_min_rnr_timer() Håkon Bugge
2021-03-30 23:12 ` Jason Gunthorpe
2021-03-31 10:38 ` Haakon Bugge
2021-03-31 12:00 ` Jason Gunthorpe
2021-03-31 12:58 ` Haakon Bugge
2021-03-31 13:15 ` Jason Gunthorpe
2021-03-31 13:34 ` Haakon Bugge
2021-03-31 13:35 ` Jason Gunthorpe
2021-03-31 14:49 ` Haakon Bugge
2021-03-31 17:09 ` Parav Pandit
2021-03-31 17:35 ` Jason Gunthorpe
2021-03-31 17:38 ` Haakon Bugge
2021-03-31 17:39 ` Jason Gunthorpe
2021-03-31 17:45 ` Haakon Bugge
2021-03-31 17:50 ` Jason Gunthorpe [this message]
2021-04-01 4:08 ` Parav Pandit
2021-03-31 13:25 ` Haakon Bugge
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=20210331175006.GQ1463678@nvidia.com \
--to=jgg@nvidia.com \
--cc=dledford@redhat.com \
--cc=haakon.bugge@oracle.com \
--cc=linux-rdma@vger.kernel.org \
--cc=parav@nvidia.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