From: Jason Gunthorpe <jgg@nvidia.com>
To: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
Cc: leonro@nvidia.com,
Brendan Cunningham <bcunningham@cornelisnetworks.com>,
Patrick Kelsey <pat.kelsey@cornelisnetworks.com>,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH for-next 3/3] IB/hfi1: Separate user SDMA page-pinning from memory type
Date: Thu, 1 Jun 2023 15:58:49 -0300 [thread overview]
Message-ID: <ZHjqacc3eKiJ0Kt0@nvidia.com> (raw)
In-Reply-To: <034e5eff-ff84-f91c-dbb0-decc04b4c340@cornelisnetworks.com>
On Thu, Jun 01, 2023 at 02:15:59PM -0400, Dennis Dalessandro wrote:
> On 6/1/23 1:45 PM, Jason Gunthorpe wrote:
> > On Fri, May 19, 2023 at 12:54:30PM -0400, Dennis Dalessandro wrote:
> >> From: Patrick Kelsey <pat.kelsey@cornelisnetworks.com>
> >>
> >> In order to handle user SDMA requests where the packet payload is to be
> >> constructed from memory other than system memory, do user SDMA
> >> page-pinning through the page-pinning interface. The page-pinning
> >> interface lets the user SDMA code operate on user_sdma_iovec objects
> >> without caring which type of memory that iovec's iov.iov_base points to.
> >
> > What is "other than system memory" memory??
>
> For instance dmabuff, or something new in the future. This is pre-req work to
> make it more abstract and general purpose and design it in a way it probably
> should have been in the first place.
But why is there uapi components to this?
And HFI doesn't support DMABUF?
Jason
next prev parent reply other threads:[~2023-06-01 18:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 16:54 [PATCH for-next 0/3] Updates for 6.5 Dennis Dalessandro
2023-05-19 16:54 ` [PATCH for-next 1/3] IB/hfi1: Add mmu_rb_node refcount to hfi1_mmu_rb_template tracepoints Dennis Dalessandro
2023-05-19 16:54 ` [PATCH for-next 2/3] IB/hfi1: Remove unused struct mmu_rb_ops fields .insert, .invalidate Dennis Dalessandro
2023-05-19 16:54 ` [PATCH for-next 3/3] IB/hfi1: Separate user SDMA page-pinning from memory type Dennis Dalessandro
2023-06-01 17:45 ` Jason Gunthorpe
2023-06-01 18:15 ` Dennis Dalessandro
2023-06-01 18:58 ` Jason Gunthorpe [this message]
2023-06-01 19:11 ` Dennis Dalessandro
2023-06-01 22:46 ` Jason Gunthorpe
2023-06-02 3:15 ` Dennis Dalessandro
2023-06-01 22:54 ` [PATCH for-next 0/3] Updates for 6.5 Jason Gunthorpe
2023-06-02 3:41 ` Dennis Dalessandro
2023-06-02 13:42 ` Jason Gunthorpe
2023-06-02 17:15 ` Dennis Dalessandro
2023-06-02 17:23 ` Jason Gunthorpe
2023-06-16 16:33 ` Dennis Dalessandro
2023-06-16 19:25 ` Jason Gunthorpe
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=ZHjqacc3eKiJ0Kt0@nvidia.com \
--to=jgg@nvidia.com \
--cc=bcunningham@cornelisnetworks.com \
--cc=dennis.dalessandro@cornelisnetworks.com \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=pat.kelsey@cornelisnetworks.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.