From: Jason Gunthorpe <jgg@nvidia.com>
To: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
Cc: leon@kernel.org, Dean Luick <dean.luick@cornelisnetworks.com>,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH for-next] RDMA/core: Add writev to uverbs file descriptor
Date: Thu, 9 Apr 2026 10:41:03 -0300 [thread overview]
Message-ID: <20260409134103.GA1851273@nvidia.com> (raw)
In-Reply-To: <177325041723.52970.2153579331168741909.stgit@awdrv-04.cornelisnetworks.com>
On Wed, Mar 11, 2026 at 01:33:37PM -0400, Dennis Dalessandro wrote:
> From: Dean Luick <dean.luick@cornelisnetworks.com>
>
> Add a writev pass-through between the uverbs file descriptor and
> infiniband devices. Interested devices may subscribe to this
> functionality.
>
> The goal is to keep all the semantics of the user interface the same so
> it's an easy migration to the uverbs cdev from the private cdev. The idea
> is that all the command and control is still ioctl, but the "data path" is
> still using the writev() to pass in the iovecs.
So the main issue was the cdev, not necessary that there was another
file descriptor.
Another options you could have a ioctl to create a compatability
anonymous fd that just does this writev flow. IIRC this was a
performance path in hfi1 so it would be better to remove some layers
of indirection.
The slower control path can run on the normal ioctl mechanism and just
run your write over this addition FD
I'm not adverse to this patch, but something to thinkg about.
Jason
prev parent reply other threads:[~2026-04-09 13:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 17:33 [PATCH for-next] RDMA/core: Add writev to uverbs file descriptor Dennis Dalessandro
2026-03-16 13:46 ` Leon Romanovsky
2026-04-09 13:41 ` Jason Gunthorpe [this message]
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=20260409134103.GA1851273@nvidia.com \
--to=jgg@nvidia.com \
--cc=dean.luick@cornelisnetworks.com \
--cc=dennis.dalessandro@cornelisnetworks.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
/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