From: John Hubbard <jhubbard@nvidia.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Bharath Vedartham <linux.bhar@gmail.com>,
Dimitri Sivanich <sivanich@hpe.com>,
Andrew Morton <akpm@linux-foundation.org>, <jglisse@redhat.com>,
<ira.weiny@intel.com>, <gregkh@linuxfoundation.org>,
<arnd@arndb.de>, <william.kucharski@oracle.com>, <hch@lst.de>,
<inux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
<linux-kernel-mentees@lists.linuxfoundation.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [Linux-kernel-mentees][PATCH v6 1/2] sgi-gru: Convert put_page() to put_user_page*()
Date: Tue, 20 Aug 2019 13:50:18 -0700 [thread overview]
Message-ID: <2971c5ea-88f2-0f07-e6f5-ad4108f62816@nvidia.com> (raw)
In-Reply-To: <20190820081820.GI3111@dhcp22.suse.cz>
On 8/20/19 1:18 AM, Michal Hocko wrote:
> On Mon 19-08-19 12:30:18, John Hubbard wrote:
>> On 8/19/19 12:06 PM, Bharath Vedartham wrote:
>>> On Mon, Aug 19, 2019 at 07:56:11AM -0500, Dimitri Sivanich wrote:
...
>> Conversion of gup/put_page sites:
>>
>> Before:
>>
>> get_user_pages(...);
>> ...
>> for each page:
>> put_page();
>>
>> After:
>>
>> gup_flags |= FOLL_PIN; (maybe FOLL_LONGTERM in some cases)
>> vaddr_pin_user_pages(...gup_flags...)
>
> I was hoping that FOLL_PIN would be handled by vaddr_pin_user_pages.
>
Good point: now that we've got the 4 cases summarized, it turns out
that either FOLL_PIN is required, or there is no need to call
vaddr_pin_user_pages() at all. So we can go back to setting FOLL_PIN
inside it, which is of course much better for maintenance. Great!
>> ...
>> vaddr_unpin_user_pages(); /* which invokes put_user_page() */
>>
>> Fortunately, it's not harmful for the simpler conversion from put_page()
>> to put_user_page() to happen first, and in fact those have usually led
>> to simplifications, paving the way to make it easier to call
>> vaddr_unpin_user_pages(), once it's ready. (And showing exactly what
>> to convert, too.)
>
> If that makes the later conversion easier then no real objections from
> me. Assuming that the current put_user_page conversions are correct of
> course (I have the mlock one and potentials that falls into the same
> category in mind).
>
Agreed: only correct conversions should be done. Not the incorrect
ones. ahem. :)
thanks,
--
John Hubbard
NVIDIA
next prev parent reply other threads:[~2019-08-20 20:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-18 19:38 [Linux-kernel-mentees][PATCH v6 0/2] get_user_pages changes Bharath Vedartham
2019-08-18 19:38 ` [Linux-kernel-mentees][PATCH v6 1/2] sgi-gru: Convert put_page() to put_user_page*() Bharath Vedartham
2019-08-18 19:51 ` Bharath Vedartham
2019-08-19 12:56 ` Dimitri Sivanich
2019-08-19 19:06 ` Bharath Vedartham
2019-08-19 19:30 ` John Hubbard
2019-08-20 8:18 ` Michal Hocko
2019-08-20 20:50 ` John Hubbard [this message]
2019-08-20 16:24 ` Bharath Vedartham
2019-08-18 19:38 ` [Linux-kernel-mentees][PATCH 2/2] sgi-gru: Remove uneccessary ifdef for CONFIG_HUGETLB_PAGE Bharath Vedartham
2019-08-18 19:51 ` Bharath Vedartham
2019-08-19 13:00 ` Dimitri Sivanich
2019-08-19 19:07 ` Bharath Vedartham
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=2971c5ea-88f2-0f07-e6f5-ad4108f62816@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=inux-kernel@vger.kernel.org \
--cc=ira.weiny@intel.com \
--cc=jglisse@redhat.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux.bhar@gmail.com \
--cc=mhocko@kernel.org \
--cc=sivanich@hpe.com \
--cc=william.kucharski@oracle.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