All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: David Hu <dhu@x6u.co>
Cc: Jacob Moroni <jmoroni@google.com>,
	sashiko-reviews@lists.linux.dev, linux-rdma@vger.kernel.org
Subject: Re: [PATCH rdma-next v3 3/6] RDMA/irdma: Support UMEM attribute for QP creation
Date: Tue, 3 Nov 2026 13:17:41 +0200	[thread overview]
Message-ID: <20261103111741.GC264423@unreal> (raw)
In-Reply-To: <CABdL-LQUdPaHu1tKW7fyXraBEUQBK-Xuv59e6u9_U7+AO7NivQ@mail.gmail.com>

On Tue, Oct 27, 2026 at 06:37:56PM -0400, David Hu wrote:
> On Mon, Oct 26, 2026 at 8:02 AM Jacob Moroni <jmoroni@google.com> wrote:
> >
> > Hi David,
> >
> > Looks good in general, but since this IRDMA driver is used with iWARP
> > NICs today,
> > can you double check this Sashiko finding? Maybe this newer path can be rejected
> > for iWARP NIC types at first? Or if there's a way to make this new path work for
> > iWARP, even better. I am not sure if there's some generic way to map the generic
> > umem for CPU access that works even for dmabufs?
> 
> Hi Jacob,
> 
> Thank you for the feedback. I double-checked the Sashiko finding -
> yes, we can make the rejection explicit. I'll send out a v4 shortly.
> 
> re: Making the path work for dma-buf + iWARP.  This seems doable; it
> just requires moderate work to plumb iWARP specific quirks to be
> dma-buf aware. However, I wasn't able to find a compelling real-world
> use case for this. If there is a strong preference to pursue this as
> part of this series, please let me know.

I wouldn't recommend investing too much effort in this. Ultimately, iWARP is
not widely used in practice, so dma-buf + iWARP is unlikely to see much use.

Thanks

  reply	other threads:[~2026-11-03 11:17 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-16 20:29 [PATCH rdma-next v3 0/6] RDMA/irdma: Add support for ioctl David Hu
2026-10-16 20:29 ` [PATCH rdma-next v3 1/6] RDMA/irdma: Plumb uverbs_attr_bundle for QP, SRQ David Hu
2026-10-16 20:31   ` sashiko-bot
2026-10-16 20:29 ` [PATCH rdma-next v3 2/6] RDMA/irdma: Register irdma UVERBS ioctl namespace David Hu
2026-10-16 20:37   ` sashiko-bot
2026-10-16 20:29 ` [PATCH rdma-next v3 3/6] RDMA/irdma: Support UMEM attribute for QP creation David Hu
2026-10-16 20:46   ` sashiko-bot
2026-10-20 23:06     ` David Hu
2026-10-26 12:01       ` Jacob Moroni
2026-10-27 22:37         ` David Hu
2026-11-03 11:17           ` Leon Romanovsky [this message]
2026-10-16 20:29 ` [PATCH rdma-next v3 4/6] RDMA/irdma: Split CQ setup to umode and kmode David Hu
2026-10-16 20:44   ` sashiko-bot
2026-10-21 19:37     ` David Hu
2026-10-16 20:29 ` [PATCH rdma-next v3 5/6] RDMA/irdma: Support UMEM attribute for CQ creation David Hu
2026-10-16 20:56   ` sashiko-bot
2026-10-21 21:06     ` David Hu
2026-11-03 11:13       ` Leon Romanovsky
2026-10-16 20:29 ` [PATCH rdma-next v3 6/6] RDMA/irdma: Support UMEM attribute for SRQ creation David Hu
2026-10-16 20:41   ` sashiko-bot

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=20261103111741.GC264423@unreal \
    --to=leon@kernel.org \
    --cc=dhu@x6u.co \
    --cc=jmoroni@google.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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.