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 v2 0/3] RDMA/efa: Add support for 128B admin v2 SQ entry
Date: Fri, 31 Jul 2026 07:50:04 +0000 [thread overview]
Message-ID: <20260731075007.3878376-1-ynachum@amazon.com> (raw)
Changelog:
v2:
* Rebase on for-next branch instead of wip/leon-for-next.
v1: https://lore.kernel.org/all/20260726123854.638687-1-ynachum@amazon.com/
-------------------------------------------------------------------------
Add support for the new 128-byte admin v2 SQ entry format. The v2 entry
extends the v1 header with checksum and payload version fields, and
carries a larger inline payload.
The series first decouples admin command payloads from admin headers,
then generalizes the SQ ring to use a configurable entry size, and
finally adds the v2 entry format selection based on device API version.
Yonatan Nachum (3):
RDMA/efa: Decouple admin command payload from admin header
RDMA/efa: Generalize the admin SQ
RDMA/efa: Add support for 128B admin v2 SQ entry
.../infiniband/hw/efa/efa_admin_cmds_defs.h | 116 +++--------
drivers/infiniband/hw/efa/efa_admin_defs.h | 33 ++-
drivers/infiniband/hw/efa/efa_com.c | 194 +++++++++++-------
drivers/infiniband/hw/efa/efa_com.h | 16 +-
drivers/infiniband/hw/efa/efa_com_cmd.c | 170 +++++----------
5 files changed, 240 insertions(+), 289 deletions(-)
--
2.50.1
next reply other threads:[~2026-07-31 7:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 7:50 Yonatan Nachum [this message]
2026-07-31 7:50 ` [PATCH for-next v2 1/3] RDMA/efa: Decouple admin command payload from admin header Yonatan Nachum
2026-07-31 7:50 ` [PATCH for-next v2 2/3] RDMA/efa: Generalize the admin SQ Yonatan Nachum
2026-07-31 7:50 ` [PATCH for-next v2 3/3] RDMA/efa: Add support for 128B admin v2 SQ entry 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=20260731075007.3878376-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.