From: John Hubbard <jhubbard@nvidia.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Mike Marshall <hubcap@omnibond.com>,
Martin Brandenburg <martin@omnibond.com>,
<devel@lists.orangefs.org>
Subject: Re: [PATCH] orangefs: convert get_user_pages() --> pin_user_pages()
Date: Sun, 17 May 2020 23:24:58 -0700 [thread overview]
Message-ID: <582e6272-ca21-6300-19dd-7776e21ce002@nvidia.com> (raw)
In-Reply-To: <20200518060139.2828423-1-jhubbard@nvidia.com>
On 2020-05-17 23:01, John Hubbard wrote:
> This code was using get_user_pages*(), in a "Case 2" scenario
> (DMA/RDMA), using the categorization from [1]. That means that it's
> time to convert the get_user_pages*() + put_page() calls to
> pin_user_pages*() + unpin_user_pages() calls.
Oops, actually, maybe that description is wrong. This is probably
closer to "Case 1: Direct IO"...right? I don't see an O_DIRECT
anywhere, but there is an ioctl to do ORANGEFS_DEV_MAP, which seems
like effectively it's doing Direct IO.
(I got lulled into commit log complacency, due to sending quite a few
non-filesystem patches that were Case 2.)
thanks,
--
John Hubbard
NVIDIA
>
> There is some helpful background in [2]: basically, this is a small
> part of fixing a long-standing disconnect between pinning pages, and
> file systems' use of those pages.
>
> [1] Documentation/core-api/pin_user_pages.rst
>
> [2] "Explicit pinning of user-space pages":
> https://lwn.net/Articles/807108/
>
> Signed-off-by: John Hubbard <jhubbard@nvidia.com>
> ---
>
> fs/orangefs/orangefs-bufmap.c | 9 +++------
> 1 file changed, 3 insertions(+), 6 deletions(-)
>
> diff --git a/fs/orangefs/orangefs-bufmap.c b/fs/orangefs/orangefs-bufmap.c
> index 2bb916d68576..538e839590ef 100644
> --- a/fs/orangefs/orangefs-bufmap.c
> +++ b/fs/orangefs/orangefs-bufmap.c
> @@ -168,10 +168,7 @@ static DEFINE_SPINLOCK(orangefs_bufmap_lock);
> static void
> orangefs_bufmap_unmap(struct orangefs_bufmap *bufmap)
> {
> - int i;
> -
> - for (i = 0; i < bufmap->page_count; i++)
> - put_page(bufmap->page_array[i]);
> + unpin_user_pages(bufmap->page_array, bufmap->page_count);
> }
>
> static void
> @@ -268,7 +265,7 @@ orangefs_bufmap_map(struct orangefs_bufmap *bufmap,
> int offset = 0, ret, i;
>
> /* map the pages */
> - ret = get_user_pages_fast((unsigned long)user_desc->ptr,
> + ret = pin_user_pages_fast((unsigned long)user_desc->ptr,
> bufmap->page_count, FOLL_WRITE, bufmap->page_array);
>
> if (ret < 0)
> @@ -280,7 +277,7 @@ orangefs_bufmap_map(struct orangefs_bufmap *bufmap,
>
> for (i = 0; i < ret; i++) {
> SetPageError(bufmap->page_array[i]);
> - put_page(bufmap->page_array[i]);
> + unpin_user_page(bufmap->page_array[i]);
> }
> return -ENOMEM;
> }
>
prev parent reply other threads:[~2020-05-18 6:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 6:01 John Hubbard
2020-05-18 6:24 ` John Hubbard [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=582e6272-ca21-6300-19dd-7776e21ce002@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=devel@lists.orangefs.org \
--cc=hubcap@omnibond.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@omnibond.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
all inboxes | Powered by JetHome®