From: Jason Gunthorpe <jgg@nvidia.com>
To: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
Cc: Leon Romanovsky <leon@kernel.org>,
Brendan Cunningham <bcunningham@cornelisnetworks.com>,
Patrick Kelsey <pat.kelsey@cornelisnetworks.com>,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH for-next v2 0/3] Rework system pinning
Date: Mon, 6 Feb 2023 11:24:57 -0400 [thread overview]
Message-ID: <Y+EbyU4HkGyzPoFO@nvidia.com> (raw)
In-Reply-To: <9367eec2-f4dc-ac18-6bd0-a184660d0fa4@cornelisnetworks.com>
On Mon, Feb 06, 2023 at 09:17:56AM -0500, Dennis Dalessandro wrote:
> On 2/6/23 6:03 AM, Leon Romanovsky wrote:
> > On Wed, Jan 25, 2023 at 03:01:33PM -0500, Dennis Dalessandro wrote:
> >> This series from Pat & Brendan reworks the system memory pinning in our driver
> >> to better handle different types of memory buffers that are passed into.
> >>
> >> Changes Since v1:
> >> ----------------
> >> Added missing commit messages to patches 1 and 2.
> >>
> >> ---
> >>
> >> Patrick Kelsey (3):
> >> IB/hfi1: Fix math bugs in hfi1_can_pin_pages()
> >> IB/hfi1: Fix sdma.h tx->num_descs off-by-one errors
> >> IB/hfi1: Do all memory-pinning through hfi1's pinning interface
> >>
> >
> > <...>
> >
> >> include/uapi/rdma/hfi/hfi1_ioctl.h | 18 +
> >> include/uapi/rdma/hfi/hfi1_user.h | 31 +-
> >> include/uapi/rdma/rdma_user_ioctl.h | 3 +
> >
> > Where can we see user-space part of these changes?
>
> These don't effect anything in rdma core if that's the concern.
>
> Pat and Brendan added an IOCTL to get some additional stat information about the
> pinned buffers to aid in testing and debugging. The thought was OPX, our
> libfabric provider for OPA may want to take advantage of the stats here as well.
I would prefer you save the uapi bits until you are ready to make an
official PR for libfabric
Jason
prev parent reply other threads:[~2023-02-06 15:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 20:01 [PATCH for-next v2 0/3] Rework system pinning Dennis Dalessandro
2023-01-25 20:01 ` [PATCH for-next v2 1/3] IB/hfi1: Fix math bugs in hfi1_can_pin_pages() Dennis Dalessandro
2023-02-16 15:12 ` Jason Gunthorpe
2023-02-16 16:18 ` Dennis Dalessandro
2023-01-25 20:01 ` [PATCH for-next v2 2/3] IB/hfi1: Fix sdma.h tx->num_descs off-by-one errors Dennis Dalessandro
2023-01-25 20:01 ` [PATCH for-next v2 3/3] IB/hfi1: Do all memory-pinning through hfi1's pinning interface Dennis Dalessandro
2023-02-06 11:03 ` [PATCH for-next v2 0/3] Rework system pinning Leon Romanovsky
2023-02-06 14:17 ` Dennis Dalessandro
2023-02-06 15:24 ` 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=Y+EbyU4HkGyzPoFO@nvidia.com \
--to=jgg@nvidia.com \
--cc=bcunningham@cornelisnetworks.com \
--cc=dennis.dalessandro@cornelisnetworks.com \
--cc=leon@kernel.org \
--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 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).