From: Yonatan Nachum <ynachum@amazon.com>
To: <jgg@nvidia.com>, <leon@kernel.org>, <linux-rdma@vger.kernel.org>
Cc: <mrgolin@amazon.com>, <sleybo@amazon.com>, <matua@amazon.com>,
<gal.pressman@linux.dev>, Yonatan Nachum <ynachum@amazon.com>
Subject: [PATCH for-next 0/2] RDMA/efa: Add 64-bit SQ request ID support
Date: Tue, 21 Jul 2026 07:00:24 +0000 [thread overview]
Message-ID: <20260721070026.1635441-1-ynachum@amazon.com> (raw)
Currently EFA WRs support 16-bit request ID, this requires EFA to manage
a translation table to translate the IB WR ID from 64-bits to 16-bits
and translating it back on CQ completion.
This series adds support for a device capability that allows SQ WRs to
carry a full 64-bit request ID, removing the need for that translation
table on devices that support it.
The first patch adds the CQ/QP creation plumbing needed to negotiate
64-bit request ID support with the device. The second patch exposes
the new device capability bit to userspace so that the driver can
report support for it.
Yonatan Nachum (2):
RDMA/efa: Add CQ/QP creation with 64-bit SQ req ID support
RDMA/efa: Expose 64-bit send WR ID support to userspace
.../infiniband/hw/efa/efa_admin_cmds_defs.h | 20 ++++++++++++++++---
drivers/infiniband/hw/efa/efa_com_cmd.c | 8 ++++++++
drivers/infiniband/hw/efa/efa_com_cmd.h | 2 ++
drivers/infiniband/hw/efa/efa_io_defs.h | 12 +++++++++--
drivers/infiniband/hw/efa/efa_verbs.c | 10 ++++++++++
include/uapi/rdma/efa-abi.h | 5 ++++-
6 files changed, 51 insertions(+), 6 deletions(-)
--
2.50.1
next reply other threads:[~2026-07-21 7:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 7:00 Yonatan Nachum [this message]
2026-07-21 7:00 ` [PATCH for-next 1/2] RDMA/efa: Add CQ/QP creation with 64-bit SQ req ID support Yonatan Nachum
2026-07-21 7:00 ` [PATCH for-next 2/2] RDMA/efa: Expose 64-bit send WR ID support to userspace Yonatan Nachum
2026-07-22 6:04 ` Gal Pressman
2026-07-22 6:34 ` Yonatan Nachum
2026-07-22 6:37 ` Yonatan Nachum
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=20260721070026.1635441-1-ynachum@amazon.com \
--to=ynachum@amazon.com \
--cc=gal.pressman@linux.dev \
--cc=jgg@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=matua@amazon.com \
--cc=mrgolin@amazon.com \
--cc=sleybo@amazon.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.