From: Jason Gunthorpe <jgg@ziepe.ca>
To: Bernard Metzler <BMT@zurich.ibm.com>
Cc: Anand Ashok Khoje <anand.a.khoje@oracle.com>,
Linux RDMA <linux-rdma@vger.kernel.org>,
Doug Ledford <dledford@redhat.com>,
Rama Nichanamatlu <rama.nichanamatlu@oracle.com>,
Manjunath Patil <manjunath.b.patil@oracle.com>
Subject: Re: [RFC] Adding private data and private data len as argument to rdma_disconnect()
Date: Fri, 13 May 2022 09:46:01 -0300 [thread overview]
Message-ID: <20220513124601.GD63055@ziepe.ca> (raw)
In-Reply-To: <BYAPR15MB26310745FFF0D04D6E73822199CA9@BYAPR15MB2631.namprd15.prod.outlook.com>
On Fri, May 13, 2022 at 09:39:44AM +0000, Bernard Metzler wrote:
> Not all providers support the transfer of private data in control
> messages after connection establishment -
> rdma_reject()/rdma_accept() being the last opportunity to send
> private data in connections lifetime for e.g. iWarp
> connections. Maybe that is why it is not exposed at the disconnect
> API call? Would RoCE support it?
RoCE and IB have a place to put it, IB does not.
The lack of support in iWarp is problematic, these APIs are supposed
to be fairly high level things.
We clearly can't just extend the existing rdma_disconnect() due to
this, and some kind of negotiation would be needed so the ULP can
learn if the extra data is supported at all.
Jason
next prev parent reply other threads:[~2022-05-13 12:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 10:02 [RFC] Adding private data and private data len as argument to rdma_disconnect() Anand Ashok Khoje
2022-05-13 4:10 ` Anand Ashok Khoje
2022-05-13 9:39 ` Bernard Metzler
2022-05-13 12:46 ` Jason Gunthorpe [this message]
2022-05-13 13:31 ` Tom Talpey
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=20220513124601.GD63055@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=BMT@zurich.ibm.com \
--cc=anand.a.khoje@oracle.com \
--cc=dledford@redhat.com \
--cc=linux-rdma@vger.kernel.org \
--cc=manjunath.b.patil@oracle.com \
--cc=rama.nichanamatlu@oracle.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.