From: john.hubbard@gmail.com
To: Matthew Wilcox <willy@infradead.org>,
Michal Hocko <mhocko@kernel.org>,
Christopher Lameter <cl@linux.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
Dan Williams <dan.j.williams@intel.com>, Jan Kara <jack@suse.cz>,
Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>,
linux-rdma <linux-rdma@vger.kernel.org>,
linux-fsdevel@vger.kernel.org, John Hubbard <jhubbard@nvidia.com>
Subject: [PATCH 0/2] mm/fs: put_user_page() proposal
Date: Mon, 9 Jul 2018 01:05:52 -0700 [thread overview]
Message-ID: <20180709080554.21931-1-jhubbard@nvidia.com> (raw)
From: John Hubbard <jhubbard@nvidia.com>
Hi,
With respect to tracking get_user_pages*() pages with page->dma_pinned*
fields [1], I spent a few days retrofitting most of the get_user_pages*()
call sites, by adding calls to a new put_user_page() function, in place
of put_page(), where appropriate. This will work, but it's a large effort.
Design note: I didn't see anything that hinted at a way to fix this
problem, without actually changing all of the get_user_pages*() call sites,
so I think it's reasonable to start with that.
Anyway, it's still incomplete, but because this is a large, tree-wide
change (that will take some time and testing), I'd like to propose a plan,
before spamming zillions of people with put_user_page() conversion patches.
So I picked out the first two patches to show where this is going.
Proposed steps:
Step 1:
Start with the patches here, then continue with...dozens more.
This will eventually convert all of the call sites to use put_user_page().
This is easy in some places, but complex in others, such as:
-- drivers/gpu/drm/amd
-- bio
-- fuse
-- cifs
-- anything from:
git grep iov_iter_get_pages | cut -f1 -d ':' | sort | uniq
The easy ones can be grouped into a single patchset, perhaps, and the
complex ones probably each need a patchset, in order to get the in-depth
review they'll need.
Furthermore, some of these areas I hope to attract some help on, once
this starts going.
Step 2:
In parallel, tidy up the core patchset that was discussed in [1], (version
2 has already been reviewed, so I know what to do), and get it perfected
and reviewed. Don't apply it until step 1 is all done, though.
Step 3:
Activate refcounting of dma-pinned pages (essentially, patch #5, which is
[1]), but don't use it yet. Place a few WARN_ON_ONCE calls to start
mopping up any missed call sites.
Step 4:
After some soak time, actually connect it up (patch #6 of [1]) and start
taking action based on the new page->dma_pinned* fields.
[1] https://www.spinics.net/lists/linux-mm/msg156409.html
or, the same thread on LKML if it's working for you:
https://lkml.org/lkml/2018/7/4/368
John Hubbard (2):
mm: introduce put_user_page(), placeholder version
goldfish_pipe/mm: convert to the new put_user_page() call
drivers/platform/goldfish/goldfish_pipe.c | 6 +++---
include/linux/mm.h | 14 ++++++++++++++
2 files changed, 17 insertions(+), 3 deletions(-)
--
2.18.0
next reply other threads:[~2018-07-09 8:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-09 8:05 john.hubbard [this message]
2018-07-09 8:05 ` [PATCH 1/2] mm: introduce put_user_page(), placeholder version john.hubbard
2018-07-09 10:08 ` kbuild test robot
2018-07-09 18:48 ` John Hubbard
2018-07-09 15:53 ` Jason Gunthorpe
2018-07-09 16:11 ` Jan Kara
2018-07-09 8:05 ` [PATCH 2/2] goldfish_pipe/mm: convert to the new put_user_page() call john.hubbard
2018-07-09 8:49 ` [PATCH 0/2] mm/fs: put_user_page() proposal Nicholas Piggin
2018-07-09 16:08 ` Jan Kara
2018-07-09 17:16 ` Matthew Wilcox
2018-07-09 19:47 ` Jan Kara
2018-07-09 19:56 ` Jason Gunthorpe
2018-07-10 7:51 ` Jan Kara
2018-07-09 20:00 ` Matthew Wilcox
2018-07-10 8:21 ` Jan Kara
2018-07-09 16:27 ` Jan Kara
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=20180709080554.21931-1-jhubbard@nvidia.com \
--to=john.hubbard@gmail.com \
--cc=cl@linux.com \
--cc=dan.j.williams@intel.com \
--cc=jack@suse.cz \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.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=mhocko@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--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