All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Christoph Hellwig" <hch@infradead.org>,
	"Jan Kara" <jack@suse.cz>, "Jason Gunthorpe" <jgg@ziepe.ca>,
	"Jens Axboe" <axboe@kernel.dk>,
	"Jérôme Glisse" <jglisse@redhat.com>,
	linux-nvdimm@lists.01.org, linux-mm@kvack.org,
	LKML <linux-kernel@vger.kernel.org>,
	"John Hubbard" <jhubbard@nvidia.com>
Subject: [PATCH 0/2] mm: devmap: page-freeing related cleanups
Date: Thu, 14 Nov 2019 16:11:32 -0800	[thread overview]
Message-ID: <20191115001134.2489505-1-jhubbard@nvidia.com> (raw)

Hi,

Here are the small devmap page-freeing cleanups as requested, so that
they can be reviewed separately from the larger "track dma-pinned pages
series" [1] that they were originally part of.

I did not add Jan Kara's and Jerome Glisse's reviewed-by tags, because those
were for patch 2 but as part of [1], which is different enough from this
series that I couldn't treat it as "close enough".

Testing: Dan notes that his patch (1) has passed nvdimm unit tests. However,
I have not yet done much testing of the two patches together. What
I've done so far is to boot up a system that has CONFIG_DEV_PAGEMAP_OPS=y
and run LTP tests on it, but none of those tests are exercising
free_devmap_managed_page().

Dan, if you could run this combined set through your unit tests, I'd feel
a lot better about it. I'll also work on getting my HMM test setup revived.


[1] https://lore.kernel.org/r/20191113042710.3997854-1-jhubbard@nvidia.com

Dan Williams (1):
  mm: Cleanup __put_devmap_managed_page() vs ->page_free()

John Hubbard (1):
  mm: devmap: refactor 1-based refcounting for ZONE_DEVICE pages

 drivers/nvdimm/pmem.c |  6 ----
 include/linux/mm.h    | 27 +++++++++++++--
 mm/memremap.c         | 76 ++++++++++++++++++++-----------------------
 3 files changed, 60 insertions(+), 49 deletions(-)

-- 
2.24.0
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-leave@lists.01.org

WARNING: multiple messages have this Message-ID (diff)
From: John Hubbard <jhubbard@nvidia.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Christoph Hellwig" <hch@infradead.org>,
	"Dan Williams" <dan.j.williams@intel.com>,
	"Ira Weiny" <ira.weiny@intel.com>, "Jan Kara" <jack@suse.cz>,
	"Jason Gunthorpe" <jgg@ziepe.ca>, "Jens Axboe" <axboe@kernel.dk>,
	"Jérôme Glisse" <jglisse@redhat.com>,
	linux-nvdimm@lists.01.org, linux-mm@kvack.org,
	LKML <linux-kernel@vger.kernel.org>,
	"John Hubbard" <jhubbard@nvidia.com>
Subject: [PATCH 0/2] mm: devmap: page-freeing related cleanups
Date: Thu, 14 Nov 2019 16:11:32 -0800	[thread overview]
Message-ID: <20191115001134.2489505-1-jhubbard@nvidia.com> (raw)

Hi,

Here are the small devmap page-freeing cleanups as requested, so that
they can be reviewed separately from the larger "track dma-pinned pages
series" [1] that they were originally part of.

I did not add Jan Kara's and Jerome Glisse's reviewed-by tags, because those
were for patch 2 but as part of [1], which is different enough from this
series that I couldn't treat it as "close enough".

Testing: Dan notes that his patch (1) has passed nvdimm unit tests. However,
I have not yet done much testing of the two patches together. What
I've done so far is to boot up a system that has CONFIG_DEV_PAGEMAP_OPS=y
and run LTP tests on it, but none of those tests are exercising
free_devmap_managed_page().

Dan, if you could run this combined set through your unit tests, I'd feel
a lot better about it. I'll also work on getting my HMM test setup revived.


[1] https://lore.kernel.org/r/20191113042710.3997854-1-jhubbard@nvidia.com

Dan Williams (1):
  mm: Cleanup __put_devmap_managed_page() vs ->page_free()

John Hubbard (1):
  mm: devmap: refactor 1-based refcounting for ZONE_DEVICE pages

 drivers/nvdimm/pmem.c |  6 ----
 include/linux/mm.h    | 27 +++++++++++++--
 mm/memremap.c         | 76 ++++++++++++++++++++-----------------------
 3 files changed, 60 insertions(+), 49 deletions(-)

-- 
2.24.0


             reply	other threads:[~2019-11-15  0:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15  0:11 John Hubbard [this message]
2019-11-15  0:11 ` [PATCH 0/2] mm: devmap: page-freeing related cleanups John Hubbard
2019-11-15  0:11 ` [PATCH 1/2] mm: Cleanup __put_devmap_managed_page() vs ->page_free() John Hubbard
2019-11-15  0:11   ` John Hubbard
2019-11-18  7:04   ` Christoph Hellwig
2019-11-18  7:04     ` Christoph Hellwig
2019-11-15  0:11 ` [PATCH 2/2] mm: devmap: refactor 1-based refcounting for ZONE_DEVICE pages John Hubbard
2019-11-15  0:11   ` John Hubbard
2019-11-15  9:48   ` Jan Kara
2019-11-15  9:48     ` Jan Kara
2019-11-15 16:41   ` Dan Williams
2019-11-15 16:41     ` Dan Williams
2019-11-18  7:08   ` Christoph Hellwig
2019-11-18  7:08     ` Christoph Hellwig
2019-11-18 16:57     ` Dan Williams
2019-11-18 16:57       ` Dan Williams

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=20191115001134.2489505-1-jhubbard@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=axboe@kernel.dk \
    --cc=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=jgg@ziepe.ca \
    --cc=jglisse@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-nvdimm@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.