From: Jason Gunthorpe <jgg@nvidia.com>
To: Parav Pandit <parav@nvidia.com>
Cc: Haakon Bugge <haakon.bugge@oracle.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:35:14 -0300 [thread overview]
Message-ID: <20210331173514.GO1463678@nvidia.com> (raw)
In-Reply-To: <BY5PR12MB4322EB01D0A22E6806B6F195DC7C9@BY5PR12MB4322.namprd12.prod.outlook.com>
On Wed, Mar 31, 2021 at 05:09:27PM +0000, Parav Pandit wrote:
>
>
> > From: Haakon Bugge <haakon.bugge@oracle.com>
> > Sent: Wednesday, March 31, 2021 8:20 PM
> >
> > > On 31 Mar 2021, at 15:35, Jason Gunthorpe <jgg@nvidia.com> wrote:
> > >
> > > On Wed, Mar 31, 2021 at 01:34:06PM +0000, Haakon Bugge wrote:
> > >
> > >>> Actually I bet you could do this same thing entirely in userspace by
> > >>> adjusting rdma_init_qp_attr() to copy the data that would be stored
> > >>> in the cm_id.. ??
> > >>
> > >> This will definitely not solve the issue for kernel ULP, e.g., RDS.
> > >
> > > Sure, that makes sense to have some rdmacm api in-kernel only
> >
> > Let me send a v2 doing only that.
> >
> > >> Further, why do we have rdma_set_option() with option
> > RDMA_OPTION_ID_ACK_TIMEOUT ?
> > >
> > > It may have been a mistake to do it like that
> >
> Timeout value goes in the CM request message so setting it through
> the cm_id object was likely correct. This reflects into cm msg as
> well as in the QP of the cm_id.
Ah, yes if it goes in the wire in a CM message it has to go to the
kernel.
Jason
next prev parent reply other threads:[~2021-03-31 17:36 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 [this message]
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
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=20210331173514.GO1463678@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 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.