From: Anand Ashok Khoje <anand.a.khoje@oracle.com>
To: Linux RDMA <linux-rdma@vger.kernel.org>,
Jason Gunthorpe <jgg@ziepe.ca>,
Doug Ledford <dledford@redhat.com>
Cc: Rama Nichanamatlu <rama.nichanamatlu@oracle.com>,
Manjunath Patil <manjunath.b.patil@oracle.com>
Subject: [RFC] Adding private data and private data len as argument to rdma_disconnect()
Date: Thu, 5 May 2022 15:32:21 +0530 [thread overview]
Message-ID: <057cdabf-997b-6f4a-6877-0be89254166b@oracle.com> (raw)
Hi,
I just wanted to float an idea for an enhancement and get opinions.
There is a provision in ib_cm layer API ib_send_cm_dreq() to send a
private_data along with the DREQ.
This private_data is helpful in situations where the receiver of DREQ
may want
to understand the reason for the DREQ and do some action on the basis of
that
reason.
We have come across issues where it was critical for the RDS code to
understand
the reason behind a DREQ and recover/tweak some parameters.
Now, rdma_cm layer has a wrapper around ib_send_cm_dreq() i.e
rdma_disconnect().
rdma_disconnect() is used by the consumers of rdma_cm. rdma_disconnect()
does
not have an argument that accepts private data. Due to this, consumers
are not
able to use this feature.
In case if we add the arguments private_data and private_data_length to
rds_disconnect(), the only challenge would be to add those to the callers
of it (NULL and 0).
Please let me know your thoughts on this.
Thanks
Anand
next reply other threads:[~2022-05-05 10:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 10:02 Anand Ashok Khoje [this message]
2022-05-13 4:10 ` [RFC] Adding private data and private data len as argument to rdma_disconnect() Anand Ashok Khoje
2022-05-13 9:39 ` Bernard Metzler
2022-05-13 12:46 ` Jason Gunthorpe
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=057cdabf-997b-6f4a-6877-0be89254166b@oracle.com \
--to=anand.a.khoje@oracle.com \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--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.