From: John Hubbard <jhubbard@nvidia.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Jason Gunthorpe <jgg@ziepe.ca>
Cc: Ira Weiny <ira.weiny@intel.com>, <linux-rdma@vger.kernel.org>,
<linux-mm@kvack.org>, LKML <linux-kernel@vger.kernel.org>,
John Hubbard <jhubbard@nvidia.com>
Subject: [PATCH 0/1] IB/umem: use get_user_pages_fast() to pin DMA pages
Date: Fri, 8 Nov 2019 18:04:33 -0800 [thread overview]
Message-ID: <20191109020434.389855-1-jhubbard@nvidia.com> (raw)
Hi Jason, Andrew,
Jason: Here is the change to get_user_pages_fast(), that you requested
during the review of "mm/gup: track dma-pinned pages: FOLL_PIN,
FOLL_LONGTERM" [1].
This is a stand-alone patch that applies to today's 5.4.0-rc6 linux.git.
If anyone could please provide any run-time testing (and of course,
Reviewed-by's), that would be huge. I've compiled and run it, but
bpftrace tells me (as I already knew) that my current anemic IB setup
is not actually exercising this code path.
Andrew: unless instructed otherwise, I plan to also re-post this as part
of the next (v3) version of [1], and hopefully have the whole series go
through your tree. That would avoid merge conflicts, and as I understand
it, there is no particular urgency for this patch, so we might as well
do it the easy way.
John Hubbard (1):
IB/umem: use get_user_pages_fast() to pin DMA pages
drivers/infiniband/core/umem.c | 17 ++++++-----------
1 file changed, 6 insertions(+), 11 deletions(-)
--
2.24.0
next reply other threads:[~2019-11-09 2:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-09 2:04 John Hubbard [this message]
2019-11-09 2:04 ` [PATCH 1/1] IB/umem: use get_user_pages_fast() to pin DMA pages John Hubbard
2019-11-11 3:21 ` Ira Weiny
2019-11-11 21:44 ` John Hubbard
2019-11-12 20:29 ` 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=20191109020434.389855-1-jhubbard@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=ira.weiny@intel.com \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).