Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
Cc: Jiri Pirko <jiri@resnulli.us>,
	linux-rdma@vger.kernel.org, jgg@ziepe.ca, mrgolin@amazon.com
Subject: Re: [PATCH rdma-next v2 4/6] RDMA/uverbs: Add ioctl method for CQ resize
Date: Sun, 28 Jun 2026 17:20:26 +0300	[thread overview]
Message-ID: <20260628142026.GB33710@unreal> (raw)
In-Reply-To: <cb0200ba-e1f1-4106-9e1e-74e4118d9106@cornelisnetworks.com>

On Thu, Jun 18, 2026 at 11:40:29AM -0400, Dennis Dalessandro wrote:
> On 6/17/26 7:06 AM, Leon Romanovsky wrote:
> > On Mon, Jun 15, 2026 at 10:50:38AM +0200, Jiri Pirko wrote:
> > > From: Jiri Pirko <jiri@nvidia.com>
> > > 
> > > Resize CQ is currently only reachable through the legacy write()
> > > uverbs command (IB_USER_VERBS_CMD_RESIZE_CQ). Add an equivalent modern
> > > ioctl method, UVERBS_METHOD_CQ_RESIZE, on the CQ object so the
> > > operation is available through the ioctl interface and can carry
> > > per-attribute extensions. The handler mirrors the legacy command: it
> > > looks up the CQ, calls resize_user_cq() and returns the new cqe count.
> > > The legacy write path is left in place for ABI compatibility.
> > 
> > I have a general question. Do we actually need CQ resizing, given that it is
> > rarely implemented and often incorrect in existing drivers? Maybe this is a
> > good time to consider deprecating that path.
> 
> Can you expand on what you mean by incorrect in existing drivers? I mean I
> see a glaring coding bug in our implementation but I can patch that.

I had "create/resize CQ" series which fixed locking in all .resize_user_cq()
implementations. The series stalled to give Jiri some space with his umem work.

Part of that series can be found here: https://git.kernel.org/pub/scm/linux/kernel/git/leon/linux-rdma.git/commit/?h=create-cq-entries-v1&id=c4f7b5999b4015609481657b437a92346a018d2c

Thanks

> 
> -Denny
> 
> 

  reply	other threads:[~2026-06-28 14:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-15  8:50 [PATCH rdma-next v2 0/6] RDMA: add per-attribute UMEM for SRQ create and CQ resize Jiri Pirko
2026-06-15  8:50 ` [PATCH rdma-next v2 1/6] RDMA/uverbs: Add SRQ buffer UMEM attribute Jiri Pirko
2026-06-15  8:50 ` [PATCH rdma-next v2 2/6] RDMA/mlx5: Use UMEM attribute for SRQ buffer in create_srq Jiri Pirko
2026-06-15  8:50 ` [PATCH rdma-next v2 3/6] RDMA/mlx5: Use UMEM attribute for SRQ doorbell record Jiri Pirko
2026-06-15  8:50 ` [PATCH rdma-next v2 4/6] RDMA/uverbs: Add ioctl method for CQ resize Jiri Pirko
2026-06-17 11:06   ` Leon Romanovsky
2026-06-18 15:40     ` Dennis Dalessandro
2026-06-28 14:20       ` Leon Romanovsky [this message]
2026-06-23 10:26     ` Jiri Pirko
2026-06-15  8:50 ` [PATCH rdma-next v2 5/6] RDMA/uverbs: Add CQ resize buffer UMEM attribute Jiri Pirko
2026-06-15  8:50 ` [PATCH rdma-next v2 6/6] RDMA/mlx5: Use UMEM attribute for CQ resize buffer Jiri Pirko

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=20260628142026.GB33710@unreal \
    --to=leon@kernel.org \
    --cc=dennis.dalessandro@cornelisnetworks.com \
    --cc=jgg@ziepe.ca \
    --cc=jiri@resnulli.us \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mrgolin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox