From: Abhijit Gangurde <abhijit.gangurde@amd.com>
To: <jgg@ziepe.ca>, <leon@kernel.org>
Cc: <allen.hubbe@amd.com>, <nikhil.agarwal@amd.com>,
<linux-rdma@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"Abhijit Gangurde" <abhijit.gangurde@amd.com>
Subject: [for-next v1 0/2] RDMA/ionic: Accept CQ, SQ, and RQ rings as umem attributes
Date: Wed, 18 Nov 2026 20:53:11 +0530 [thread overview]
Message-ID: <20261118152313.113714-1-abhijit.gangurde@amd.com> (raw)
Let userspace hand ionic queue rings to create_cq and create_qp as
struct ib_uverbs_buffer_desc, instead of only as a raw address in the
driver request. A ring may be a virtual address or a page-aligned
slice of a dma-buf, so several rings can share one dma-buf.
The get_context bit IONIC_CTX_CMASK_CQ_QP_BUF_UMEM tells userspace it
may send the descriptors. ionic_cq_req and ionic_qp_req are unchanged,
so a provider that does not send them still uses the existing write
path and ib_umem_get_va.
Userspace: https://github.com/linux-rdma/rdma-core/pull/1862
Abhijit Gangurde (2):
RDMA/ionic: Accept CQ ring buffers as ioctl umem attributes
RDMA/ionic: Accept QP SQ and RQ rings as ioctl umem attributes
drivers/infiniband/hw/ionic/ionic_admin.c | 2 +-
.../infiniband/hw/ionic/ionic_controlpath.c | 183 +++++++++++++++---
drivers/infiniband/hw/ionic/ionic_ibdev.c | 17 ++
drivers/infiniband/hw/ionic/ionic_ibdev.h | 2 +
include/uapi/rdma/ionic-abi.h | 1 +
include/uapi/rdma/ionic_user_ioctl_cmds.h | 15 ++
6 files changed, 187 insertions(+), 33 deletions(-)
create mode 100644 include/uapi/rdma/ionic_user_ioctl_cmds.h
--
2.43.0
next reply other threads:[~2026-11-18 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 15:23 Abhijit Gangurde [this message]
2026-11-18 15:23 ` [for-next v1 1/2] RDMA/ionic: Accept CQ ring buffers as ioctl " Abhijit Gangurde
2026-11-18 15:23 ` [for-next v1 2/2] RDMA/ionic: Accept QP SQ and RQ rings " Abhijit Gangurde
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=20261118152313.113714-1-abhijit.gangurde@amd.com \
--to=abhijit.gangurde@amd.com \
--cc=allen.hubbe@amd.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=nikhil.agarwal@amd.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®