From: John Hubbard <jhubbard@nvidia.com>
To: Christoph Hellwig <hch@lst.de>
Cc: Dan Williams <dan.j.williams@intel.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
john.hubbard@gmail.com, Matthew Wilcox <willy@infradead.org>,
Michal Hocko <mhocko@kernel.org>,
Christopher Lameter <cl@linux.com>, Jan Kara <jack@suse.cz>,
Linux MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-rdma <linux-rdma@vger.kernel.org>
Subject: Re: [PATCH 2/2] mm: set PG_dma_pinned on get_user_pages*()
Date: Mon, 18 Jun 2018 10:50:57 -0700 [thread overview]
Message-ID: <d4817192-6db0-2f3f-7c67-6078b69686d3@nvidia.com> (raw)
In-Reply-To: <20180618081258.GB16991@lst.de>
On 06/18/2018 01:12 AM, Christoph Hellwig wrote:
> On Sun, Jun 17, 2018 at 01:28:18PM -0700, John Hubbard wrote:
>> Yes. However, my thinking was: get_user_pages() can become a way to indicate that
>> these pages are going to be treated specially. In particular, the caller
>> does not really want or need to support certain file operations, while the
>> page is flagged this way.
>>
>> If necessary, we could add a new API call.
>
> That API call is called get_user_pages_longterm.
OK...I had the impression that this was just semi-temporary API for dax, but
given that it's an exported symbol, I guess it really is here to stay.
Anyway, are you thinking that we could set the new page flag here? Or just pointing
out that the other get_user_pages* variants are the wrong place?
next prev parent reply other threads:[~2018-06-18 17:51 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-17 1:25 [PATCH 0/2] mm: gup: don't unmap or drop filesystem buffers john.hubbard
2018-06-17 1:25 ` [PATCH 1/2] consolidate get_user_pages error handling john.hubbard
2018-06-17 1:25 ` [PATCH 2/2] mm: set PG_dma_pinned on get_user_pages*() john.hubbard
2018-06-17 19:53 ` Dan Williams
2018-06-17 20:04 ` Jason Gunthorpe
2018-06-17 20:10 ` Dan Williams
2018-06-17 20:28 ` John Hubbard
2018-06-18 8:12 ` Christoph Hellwig
2018-06-18 17:50 ` John Hubbard [this message]
2018-06-18 17:56 ` Dan Williams
2018-06-18 18:14 ` John Hubbard
2018-06-18 19:21 ` Dan Williams
2018-06-18 19:31 ` Jason Gunthorpe
2018-06-18 20:04 ` Dan Williams
2018-06-18 21:36 ` John Hubbard
2018-06-19 8:29 ` Jan Kara
2018-06-19 9:02 ` Matthew Wilcox
2018-06-19 10:41 ` Jan Kara
2018-06-19 18:11 ` John Hubbard
2018-06-20 1:24 ` Dan Williams
2018-06-20 1:34 ` John Hubbard
2018-06-20 1:57 ` Dan Williams
2018-06-20 2:03 ` John Hubbard
2018-06-20 12:08 ` Jan Kara
2018-06-20 22:55 ` John Hubbard
2018-06-21 16:30 ` Jan Kara
2018-06-25 15:21 ` Jan Kara
2018-06-25 19:03 ` John Hubbard
2018-06-26 7:52 ` Jan Kara
2018-06-26 6:31 ` John Hubbard
2018-06-26 11:48 ` Jan Kara
2018-06-26 13:47 ` Michal Hocko
2018-06-26 16:48 ` Jan Kara
2018-06-27 11:32 ` Michal Hocko
2018-06-27 11:53 ` Jan Kara
2018-06-27 11:59 ` Michal Hocko
2018-06-27 12:42 ` Jan Kara
2018-06-27 14:57 ` Jason Gunthorpe
2018-06-27 17:02 ` Jan Kara
2018-06-28 2:42 ` John Hubbard
2018-06-28 9:17 ` Jan Kara
2018-07-02 5:52 ` Leon Romanovsky
2018-07-02 6:10 ` John Hubbard
2018-07-02 6:34 ` Leon Romanovsky
2018-07-02 6:41 ` John Hubbard
2018-07-02 10:36 ` Michal Hocko
2018-07-02 7:02 ` Jan Kara
2018-07-02 14:48 ` Michal Hocko
2018-07-02 6:58 ` Jan Kara
2018-06-18 8:11 ` Christoph Hellwig
2018-06-19 6:15 ` Leon Romanovsky
2018-06-17 22:19 ` John Hubbard
2018-06-18 7:56 ` Christoph Hellwig
2018-06-18 17:44 ` John Hubbard
2018-06-17 21:54 ` [PATCH 0/2] mm: gup: don't unmap or drop filesystem buffers Christopher Lameter
2018-06-17 22:23 ` John Hubbard
2018-06-18 8:10 ` Christoph Hellwig
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=d4817192-6db0-2f3f-7c67-6078b69686d3@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=cl@linux.com \
--cc=dan.j.williams@intel.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=jgg@ziepe.ca \
--cc=john.hubbard@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=willy@infradead.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