All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: David Hu <dhu@x6u.co>
Cc: Mustafa Ismail <mustafa.ismail@intel.com>,
	Shiraz Saleem <shiraz.saleem@intel.com>,
	Jason Gunthorpe <jgg@ziepe.ca>, Jacob Moroni <jmoroni@google.com>,
	intel-wired-lan@lists.osuosl.org, linux-rdma@vger.kernel.org,
	linux-kernel@vger.kernel.org, David Hu <xuehaohu@google.com>
Subject: Re: [PATCH rdma-next v4 0/6] RDMA/irdma: Add support for ioctl
Date: Wed, 4 Nov 2026 09:50:55 +0200	[thread overview]
Message-ID: <20261104075055.GL264423@unreal> (raw)
In-Reply-To: <20261030181512.2056056-1-dhu@x6u.co>

On Fri, Oct 30, 2026 at 06:15:06PM +0000, David Hu wrote:
> From: David Hu <xuehaohu@google.com>
> 
> Hello,
> 
> This patch series introduces support for uverbs ioctl queue creation
> (QP, CQ, and SRQ) in the irdma driver. This series makes progress towards
> modernizing irdma. This enables 1-step queue creation from pinned UMEMs
> and shared dma-buf heaps (system_cc_shared), providing RDMA support for
> Confidential Computing (CoCo) guest environments where memory encryption
> otherwise prevents standard host-VA-based queues from operating.
> 
> Historically, irdma relied on legacy write() commands for queue setup.
> This series modernizes irdma's queue creation path by adopting the ioctl
> infrastructure:
> 
> 1. Plumbs uverbs_attr_bundle into the irdma QP and SRQ creation routines.
> 2. Registers irdma's UVERBS ioctl namespace definition for QP, CQ, and SRQ.
> 3. Implements 1-step queue buffer creation for QP, CQ, and SRQ using
>    UVERBS_ATTR_CREATE_*_BUF_UMEM attributes and ib_umem_get_attr(),
>    configuring hardware Page Buffer Lists (PBLs) directly from pinned umems.
> 4. Split CQ creation setup logic by umode and kmode into separate
>    routines to be consistent with other queue creation logic.
> 5. Adds support for driver-specific shadow area UMEM attributes during CQ
>    creation with CQ resize capability.
> 6. Preserves backward compatibility with legacy 2-step write() path
>    registrations when UMEM attributes are not provided.
> 
> User space rdma-core PR: https://github.com/linux-rdma/rdma-core/pull/1766
> 
> Testing:
> Verified with rc_pingpong, srq_pingpong, and dmabuf_pingpong over irdma
> devices in Confidential VM environments.
> 
> Changes in v4:
> - Reject dma-buf queue creation in iWARP mode and enforce page-offset
>   alignment unconditionally in irdma_setup_q_pbl_from_umem() (Jacob)
> - Bound attr->cqe in irdma_create_user_cq() to prevent cq_pages overflow (Sashiko)
> - Fix to irdma_cq_free_rsrc() was sent separately (Sashiko)
> - Link to v3: https://lore.kernel.org/all/20261016202909.1289496-1-dhu@x6u.co/

I applied the series, but I have a concern: the commit messages are
not useful.

Thanks

  parent reply	other threads:[~2026-11-04  7:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-30 18:15 [PATCH rdma-next v4 0/6] RDMA/irdma: Add support for ioctl David Hu
2026-10-30 18:15 ` [PATCH rdma-next v4 1/6] RDMA/irdma: Plumb uverbs_attr_bundle for QP, SRQ David Hu
2026-10-30 18:23   ` sashiko-bot
2026-11-05 12:50   ` Loktionov, Aleksandr
2026-10-30 18:15 ` [PATCH rdma-next v4 2/6] RDMA/irdma: Register irdma UVERBS ioctl namespace David Hu
2026-10-30 18:23   ` sashiko-bot
2026-11-05 12:51   ` Loktionov, Aleksandr
2026-10-30 18:15 ` [PATCH rdma-next v4 3/6] RDMA/irdma: Support UMEM attribute for QP creation David Hu
2026-10-30 18:26   ` sashiko-bot
2026-10-30 18:15 ` [PATCH rdma-next v4 4/6] RDMA/irdma: Split CQ setup to umode and kmode David Hu
2026-10-30 18:30   ` sashiko-bot
2026-10-30 18:15 ` [PATCH rdma-next v4 5/6] RDMA/irdma: Support UMEM attribute for CQ creation David Hu
2026-10-30 18:33   ` sashiko-bot
2026-11-02 21:28     ` David Hu
2026-10-30 18:15 ` [PATCH rdma-next v4 6/6] RDMA/irdma: Support UMEM attribute for SRQ creation David Hu
2026-10-30 18:34   ` sashiko-bot
2026-11-04  7:50 ` Leon Romanovsky [this message]
2026-11-04 17:23   ` [PATCH rdma-next v4 0/6] RDMA/irdma: Add support for ioctl David Hu
2026-11-04  7:51 ` Leon Romanovsky

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=20261104075055.GL264423@unreal \
    --to=leon@kernel.org \
    --cc=dhu@x6u.co \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jgg@ziepe.ca \
    --cc=jmoroni@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mustafa.ismail@intel.com \
    --cc=shiraz.saleem@intel.com \
    --cc=xuehaohu@google.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.