From: John Hubbard <jhubbard@nvidia.com>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux-MM <linux-mm@kvack.org>
Subject: Re: [PATCH 1/2] mm/gup: introduce pin_user_pages_locked()
Date: Sun, 31 May 2020 12:56:23 -0700 [thread overview]
Message-ID: <0674f8b7-a5eb-6d5c-792d-573f85871a72@nvidia.com> (raw)
In-Reply-To: <CAFqt6zaz21GQZYSGZ5Md0hCrPv8UFQ7gQMiV_oBzX0zSTZ16-A@mail.gmail.com>
On 2020-05-31 00:13, Souptick Joarder wrote:
> On Sun, May 31, 2020 at 12:34 PM Souptick Joarder <jrdr.linux@gmail.com> wrote:
>>
>> On Thu, May 28, 2020 at 4:02 AM John Hubbard <jhubbard@nvidia.com> wrote:
>>>
>>> Introduce pin_user_pages_locked(), which is nearly identical to
>>> get_user_pages_locked() except that it sets FOLL_PIN and rejects
>>> FOLL_GET.
>
> Forget to ask, is it fine to add this new pin_user_pages_locked() in
> Documentation/core-api/pin_user_pages.rst ?
>
I wasn't planning on maintaining a rigorous list of all of the pin_user_page*()
API calls, in pin_user_pages.rst. Each call is documented in gup.c, for that.
The .rst is there to help explain things at a slighly higher abstraction level.
thanks,
--
John Hubbard
NVIDIA
next prev parent reply other threads:[~2020-05-31 19:56 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 [this message]
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
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=0674f8b7-a5eb-6d5c-792d-573f85871a72@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=jrdr.linux@gmail.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).