From: Jason Gunthorpe <jgg@ziepe.ca>
To: Jiri Pirko <jiri@resnulli.us>
Cc: Jacob Moroni <jmoroni@google.com>,
linux-rdma@vger.kernel.org, leon@kernel.org, edwards@nvidia.com,
kees@kernel.org, parav@nvidia.com, mbloch@nvidia.com,
yishaih@nvidia.com, lirongqing@baidu.com,
huangjunxian6@hisilicon.com, liuy22@mails.tsinghua.edu.cn
Subject: Re: [PATCH rdma-next 2/2] RDMA/umem: block plain userspace memory registration under CoCo bounce
Date: Wed, 6 May 2026 06:49:40 -0300 [thread overview]
Message-ID: <afsOtEeppBzxOGUB@ziepe.ca> (raw)
In-Reply-To: <afsIsW7vKgJtdNA2@FV6GYCPJ69>
On Wed, May 06, 2026 at 11:25:13AM +0200, Jiri Pirko wrote:
> Tue, May 05, 2026 at 06:02:50PM +0200, jgg@ziepe.ca wrote:
> >On Tue, May 05, 2026 at 09:20:01AM -0400, Jacob Moroni wrote:
> >> Hi,
> >>
> >> Out of curiosity, it seems like we set DMA_ATTR_REQUIRE_COHERENT, so
> >> would that have caused these registrations to fail anyway since it would
> >> be trying to use swiotlb if running in a CVM?
> >
> >It is supposed to, at least that is the intention. I think that
> >new attribute overtook Jiri's patch here?
>
> Hmm, don't we want rather -EOPNOTSUPP instead of very wide -EIO in this
> case? I think that might be better for the user.
Yeah, I would prefer that also, it is a good enough reason for this
patch.
Jason
next prev parent reply other threads:[~2026-05-06 9:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 6:11 [PATCH rdma-next 0/2] RDMA: detect and handle CoCo DMA bounce buffering Jiri Pirko
2026-05-05 6:11 ` [PATCH rdma-next 1/2] RDMA/uverbs: expose CoCo DMA bounce requirement to userspace Jiri Pirko
2026-05-05 6:11 ` [PATCH rdma-next 2/2] RDMA/umem: block plain userspace memory registration under CoCo bounce Jiri Pirko
2026-05-05 13:20 ` Jacob Moroni
2026-05-05 16:02 ` Jason Gunthorpe
2026-05-05 18:17 ` Jacob Moroni
2026-05-06 9:20 ` Jiri Pirko
2026-05-06 9:17 ` Jiri Pirko
2026-05-06 9:25 ` Jiri Pirko
2026-05-06 9:49 ` Jason Gunthorpe [this message]
2026-05-06 10:54 ` Jiri Pirko
2026-05-06 13:39 ` Jacob Moroni
2026-05-06 14:54 ` 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=afsOtEeppBzxOGUB@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=edwards@nvidia.com \
--cc=huangjunxian6@hisilicon.com \
--cc=jiri@resnulli.us \
--cc=jmoroni@google.com \
--cc=kees@kernel.org \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lirongqing@baidu.com \
--cc=liuy22@mails.tsinghua.edu.cn \
--cc=mbloch@nvidia.com \
--cc=parav@nvidia.com \
--cc=yishaih@nvidia.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.