From: John Hubbard <jhubbard@nvidia.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Santosh Shilimkar <santosh.shilimkar@oracle.com>,
Hans Westgaard Ry <hans.westgaard.ry@oracle.com>,
Leon Romanovsky <leonro@mellanox.com>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, <netdev@vger.kernel.org>,
<rds-devel@oss.oracle.com>, <linux-rdma@vger.kernel.org>,
<linux-mm@kvack.org>, LKML <linux-kernel@vger.kernel.org>,
John Hubbard <jhubbard@nvidia.com>
Subject: [PATCH 0/1] net/rds: Track user mapped pages through special API
Date: Tue, 11 Feb 2020 19:03:54 -0800 [thread overview]
Message-ID: <20200212030355.1600749-1-jhubbard@nvidia.com> (raw)
Hi Andrew and all,
Here's another gup-to-pup (get_user_pages() to pin_user_pages())
conversion patch, this time from Leon Romanovsky, that we agreed is
better suited for the linux-mm tree than for linux-rdma. And it also
couldn't be merged until now (5.6-rc1) because it relies on stuff from
a few different git trees.
(Leon: I added my standard blurb about "this changes set_page_dirty() to
set_page_dirty_lock()", to the commit description.)
I've reviewed this, and done some basic checks (cross-compiles, and
a subset of an LTP run on x86), but I have not personally done directed
tests that would provide coverage of this change.
For that, could we please get some Tested-by tags, and any other tags
(reviews, acks) from those of you who have reportedly tested this? That
would be Hans or Santosh (on Cc below), I'm told:
Cc: Hans Westgaard Ry <hans.westgaard.ry@oracle.com>
Cc: Santosh Shilimkar <santosh.shilimkar@oracle.com>
Leon Romanovsky (1):
net/rds: Track user mapped pages through special API
net/rds/rdma.c | 24 ++++++++++++------------
1 file changed, 12 insertions(+), 12 deletions(-)
base-commit: 359c92c02bfae1a6f1e8e37c298e518fd256642c
--
2.25.0
next reply other threads:[~2020-02-12 3:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 3:03 John Hubbard [this message]
2020-02-12 3:03 ` [PATCH 1/1] " John Hubbard
2020-02-12 17:31 ` santosh.shilimkar
2020-02-12 17:51 ` Leon Romanovsky
2020-02-12 17:55 ` santosh.shilimkar
2020-02-17 2:37 ` David Miller
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=20200212030355.1600749-1-jhubbard@nvidia.com \
--to=jhubbard@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=hans.westgaard.ry@oracle.com \
--cc=kuba@kernel.org \
--cc=leonro@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.com \
--cc=santosh.shilimkar@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