From: Jason Gunthorpe <firstname.lastname@example.org>
To: Dennis Dalessandro <email@example.com>
Cc: Linux RDMA <firstname.lastname@example.org>,
Doug Ledford <email@example.com>,
Subject: Re: [RFC] bulk zero copy transport
Date: Thu, 19 Aug 2021 20:01:01 -0300 [thread overview]
Message-ID: <20210819230101.GT543798@ziepe.ca> (raw)
On Thu, Aug 19, 2021 at 03:09:02PM -0400, Dennis Dalessandro wrote:
> Just wanted to float an idea we are thinking about. It builds on the basic idea
> of what Intel submitted as their RV module . This however does things a bit
> differently and is really all about bulk zero-copy using the kernel. It is a new
> The major differences are that there will be no new cdev needed. We will make
> use of the existing HFI1 cdev where an FD is needed. We also propose to make use
> of IO-Uring (hence needing FD) to get requests into the kernel. The idea will be
> to not share Uverbs objects with the kernel. The kernel will maintain
> ownership of the qp, pd, mr, cq, etc.
I feel a lot of reluctance to see the API surface of the HFI1 cdev
expanded, especially to encompass an entire ULP
As you know I think that cdev is very much the wrong way to design
driver interfaces, and since all the work is now completed to do it
through verbs I'm not keen on any expansion.
But I'm confused how you are calling something a ULP but then talking
about the HFI (or uverbs even) cdev? That isn't a ULP.
A ULP is something like RDS that spawns its own cdevs and interworks
with the common RDMA stack.
I suppose I don't get what you are trying to sketch. Maybe you could
share the uAPI you envision in more detail?
next prev parent reply other threads:[~2021-08-19 23:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 19:09 [RFC] bulk zero copy transport Dennis Dalessandro
2021-08-19 23:01 ` Jason Gunthorpe [this message]
2021-08-20 12:55 ` Dennis Dalessandro
2021-08-20 8:18 ` Stefan Metzmacher
2021-08-20 12:37 ` Dennis Dalessandro
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).