linux-kselftest.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: John Hubbard <jhubbard@nvidia.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
	"Al Viro" <viro@zeniv.linux.org.uk>,
	"Christoph Hellwig" <hch@infradead.org>,
	"Dan Williams" <dan.j.williams@intel.com>,
	"Dave Chinner" <david@fromorbit.com>,
	"Ira Weiny" <ira.weiny@intel.com>, "Jan Kara" <jack@suse.cz>,
	"Jason Gunthorpe" <jgg@ziepe.ca>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Jérôme Glisse" <jglisse@redhat.com>,
	"Kirill A . Shutemov" <kirill@shutemov.name>,
	"Michal Hocko" <mhocko@suse.com>,
	"Mike Kravetz" <mike.kravetz@oracle.com>,
	"Shuah Khan" <shuah@kernel.org>,
	"Vlastimil Babka" <vbabka@suse.cz>,
	linux-doc@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-kselftest@vger.kernel.org, linux-rdma@vger.kernel.org,
	linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] mm/gup: track FOLL_PIN pages (follow on from v12)
Date: Sat, 25 Jan 2020 18:23:39 +0200	[thread overview]
Message-ID: <20200125162339.GA41770@unreal> (raw)
In-Reply-To: <20200125021115.731629-1-jhubbard@nvidia.com>

On Fri, Jan 24, 2020 at 06:11:12PM -0800, John Hubbard wrote:
> Leon Romanovsky:
>
> If you get a chance, I'd love to have this short series (or even just
> the first patch; the others are just selftests) run through your test
> suite that was previously choking on my earlier v11 patchset. The huge
> page pincount limitations are removed, so I'm expecting a perfect test
> run this time!
>

I added those patches to our regression and I will post the in the
couple of days.

Thanks

  parent reply	other threads:[~2020-01-25 16:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-25  2:11 [PATCH 0/3] mm/gup: track FOLL_PIN pages (follow on from v12) John Hubbard
2020-01-25  2:11 ` [PATCH 1/3] mm/gup: track FOLL_PIN pages John Hubbard
2020-01-27 11:06   ` Jan Kara
2020-01-27 18:17     ` John Hubbard
2020-01-27 13:00   ` Kirill A. Shutemov
2020-01-27 18:18     ` John Hubbard
2020-01-25  2:11 ` [PATCH 2/3] mm/gup_benchmark: support pin_user_pages() and related calls John Hubbard
2020-01-27 20:52   ` Nathan Chancellor
2020-01-27 21:32     ` John Hubbard
2020-01-25  2:11 ` [PATCH 3/3] selftests/vm: run_vmtests: invoke gup_benchmark with basic FOLL_PIN coverage John Hubbard
2020-01-25 16:23 ` Leon Romanovsky [this message]
2020-01-29  5:47   ` [PATCH 0/3] mm/gup: track FOLL_PIN pages (follow on from v12) Leon Romanovsky
2020-01-29 20:01     ` John Hubbard

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=20200125162339.GA41770@unreal \
    --to=leon@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=corbet@lwn.net \
    --cc=dan.j.williams@intel.com \
    --cc=david@fromorbit.com \
    --cc=hch@infradead.org \
    --cc=ira.weiny@intel.com \
    --cc=jack@suse.cz \
    --cc=jgg@ziepe.ca \
    --cc=jglisse@redhat.com \
    --cc=jhubbard@nvidia.com \
    --cc=kirill@shutemov.name \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mhocko@suse.com \
    --cc=mike.kravetz@oracle.com \
    --cc=shuah@kernel.org \
    --cc=vbabka@suse.cz \
    --cc=viro@zeniv.linux.org.uk \
    /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).