linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: John Hubbard <jhubbard@nvidia.com>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-mm@kvack.org
Subject: Re: [PATCH 2/2] mm/gup: frame_vector: convert get_user_pages() --> pin_user_pages()
Date: Thu, 28 May 2020 10:46:40 +0200	[thread overview]
Message-ID: <cfe6f037-8b5a-79d7-ba19-f7a16c31fa9a@redhat.com> (raw)
In-Reply-To: <20200527223243.884385-3-jhubbard@nvidia.com>

On 28.05.20 00:32, John Hubbard wrote:
> This code was using get_user_pages*(), and all of the callers so far
> were 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.
> 
> 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>
> ---
>  mm/frame_vector.c | 7 +++----
>  1 file changed, 3 insertions(+), 4 deletions(-)
> 
> diff --git a/mm/frame_vector.c b/mm/frame_vector.c
> index c431ca81dad5..4107dbca0056 100644
> --- a/mm/frame_vector.c
> +++ b/mm/frame_vector.c
> @@ -72,7 +72,7 @@ int get_vaddr_frames(unsigned long start, unsigned int nr_frames,
>  	if (!(vma->vm_flags & (VM_IO | VM_PFNMAP))) {
>  		vec->got_ref = true;
>  		vec->is_pfns = false;
> -		ret = get_user_pages_locked(start, nr_frames,
> +		ret = pin_user_pages_locked(start, nr_frames,
>  			gup_flags, (struct page **)(vec->ptrs), &locked);
>  		goto out;
>  	}
> @@ -122,7 +122,6 @@ EXPORT_SYMBOL(get_vaddr_frames);
>   */
>  void put_vaddr_frames(struct frame_vector *vec)
>  {
> -	int i;
>  	struct page **pages;
>  
>  	if (!vec->got_ref)
> @@ -135,8 +134,8 @@ void put_vaddr_frames(struct frame_vector *vec)
>  	 */
>  	if (WARN_ON(IS_ERR(pages)))
>  		goto out;
> -	for (i = 0; i < vec->nr_frames; i++)
> -		put_page(pages[i]);
> +
> +	unpin_user_pages(pages, vec->nr_frames);
>  	vec->got_ref = false;
>  out:
>  	vec->nr_frames = 0;
> 

Not familiar with this code, but from what I can tell this LGTM.

-- 
Thanks,

David / dhildenb



      reply	other threads:[~2020-05-28  8:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-27 22:32 [PATCH 0/2] mm/gup: introduce pin_user_pages_locked(), use it in frame_vector.c John Hubbard
2020-05-27 22:32 ` [PATCH 1/2] mm/gup: introduce pin_user_pages_locked() John Hubbard
2020-05-28  8:43   ` David Hildenbrand
2020-05-31  7:04   ` Souptick Joarder
2020-05-31  7:13     ` Souptick Joarder
2020-05-31 19:56       ` John Hubbard
2020-05-31 19:52     ` John Hubbard
2020-05-31 13:03   ` Pankaj Gupta
2020-05-27 22:32 ` [PATCH 2/2] mm/gup: frame_vector: convert get_user_pages() --> pin_user_pages() John Hubbard
2020-05-28  8:46   ` David Hildenbrand [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=cfe6f037-8b5a-79d7-ba19-f7a16c31fa9a@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=jhubbard@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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).