From: John Hubbard <jhubbard@nvidia.com>
To: Ira Weiny <ira.weiny@intel.com>
Cc: Jason Gunthorpe <jgg@mellanox.com>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
Doug Ledford <dledford@redhat.com>,
"Mike Marciniszyn" <mike.marciniszyn@intel.com>,
Dennis Dalessandro <dennis.dalessandro@intel.com>,
Christian Benvenuti <benve@cisco.com>, "Jan Kara" <jack@suse.cz>
Subject: Re: [PATCH 1/1] infiniband/mm: convert put_page() to put_user_page*()
Date: Thu, 23 May 2019 15:54:08 -0700 [thread overview]
Message-ID: <6a18af65-7071-2531-d767-42ba74ad82c4@nvidia.com> (raw)
In-Reply-To: <050f56d0-1dda-036e-e508-3a7255ac7b59@nvidia.com>
On 5/23/19 3:50 PM, John Hubbard wrote:
> [...]
> I was thinking of it as a temporary measure, only up until, but not including the
> point where put_user_pages() becomes active. That is, the point when put_user_pages
> starts decrementing GUP_PIN_COUNTING_BIAS, instead of just forwarding to put_page().
>
> (For other readers, that's this patch:
>
> "mm/gup: debug tracking of get_user_pages() references"
>
> ...in https://github.com/johnhubbard/linux/tree/gup_dma_core )
>
Arggh, correction, I meant this patch:
"mm/gup: track gup-pinned pages"
...sorry for any confusion there.
thanks,
--
John Hubbard
NVIDIA
next prev parent reply other threads:[~2019-05-23 22:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 7:25 [PATCH 0/1] infiniband/mm: convert put_page() to put_user_page*() john.hubbard
2019-05-23 7:25 ` [PATCH 1/1] " john.hubbard
2019-05-23 15:31 ` Jerome Glisse
2019-05-23 17:56 ` John Hubbard
2019-05-23 17:28 ` Ira Weiny
2019-05-23 17:32 ` Jason Gunthorpe
2019-05-23 17:46 ` John Hubbard
2019-05-23 19:04 ` Ira Weiny
2019-05-23 19:13 ` John Hubbard
2019-05-23 22:37 ` Ira Weiny
2019-05-23 22:50 ` John Hubbard
2019-05-23 22:54 ` John Hubbard [this message]
2019-05-23 19:17 ` 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=6a18af65-7071-2531-d767-42ba74ad82c4@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=benve@cisco.com \
--cc=dennis.dalessandro@intel.com \
--cc=dledford@redhat.com \
--cc=ira.weiny@intel.com \
--cc=jack@suse.cz \
--cc=jgg@mellanox.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mike.marciniszyn@intel.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;
as well as URLs for NNTP newsgroup(s).