Linux kernel -stable discussions
 help / color / mirror / Atom feed
From: Dan Williams <dan.j.williams@intel.com>
To: linux-nvdimm@lists.01.org
Cc: Vishal Verma <vishal.l.verma@intel.com>,
	Ross Zwisler <ross.zwisler@linux.intel.com>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: [PATCH 00/13] prep for device-dax, untangle pfn-device setup
Date: Wed, 23 Mar 2016 18:25:21 -0700	[thread overview]
Message-ID: <20160324012520.21436.22505.stgit@dwillia2-desk3.jf.intel.com> (raw)

The infrastructure for setting up a pfn-device (struct page memmap array
allocation for reserved memory) is generally useful.  Untangle it from
the pmem driver and make it available as core libnvdimm functionality.
The motivation for this work is an investigation into a standalone
device-dax facility, but the changes stand on their own.

Outside of exporting nvdimm_setup_pfn() as a generic facility this also
includes the following benefits:

1/ fix a section alignment vs badblocks tracking bug

2/ struct pmem_device sheds 24 bytes

3/ struct blk_device is replaced with some (smaller in total) extensions
   to struct nd_namespace_blk.

4/ Reduce pointer chasing by retrieving driver private data from
   ->queuedata rather than bio->bi_bdev->bd_disk->private_data.

---

Dan Williams (13):
      libnvdimm, pfn: fix nvdimm_namespace_add_poison() vs section alignment
      libnvdimm, pmem: kill pmem->ndns
      libnvdimm, pfn, convert nd_pfn_probe() to devm
      libnvdimm, btt, convert nd_btt_probe() to devm
      libnvdimm, blk: use devm_add_action to release bdev resources
      libnvdimm, blk: use ->queuedata for driver private data
      libnvdimm, pmem: use ->queuedata for driver private data
      libnvdimm, blk: move i/o infrastructure to nd_namespace_blk
      libnvdimm, pmem: use devm_add_action to release bdev resources
      libnvdimm, pmem: clean up resource print / request
      libnvdimm, pmem, pfn: make pmem_rw_bytes generic and refactor pfn setup
      libnvdimm, pmem, pfn: move pfn setup to the core
      libnvdimm, pmem: kill ->pmem_queue and ->pmem_disk


 drivers/nvdimm/blk.c              |  208 ++++++++--------
 drivers/nvdimm/btt.c              |   20 +-
 drivers/nvdimm/btt_devs.c         |   24 +-
 drivers/nvdimm/claim.c            |   61 +++++
 drivers/nvdimm/core.c             |   41 ++-
 drivers/nvdimm/nd.h               |   50 +++-
 drivers/nvdimm/pfn_devs.c         |  208 +++++++++++++++-
 drivers/nvdimm/pmem.c             |  475 +++++++++----------------------------
 include/linux/nd.h                |   11 +
 tools/testing/nvdimm/Kbuild       |    1 
 tools/testing/nvdimm/test/iomap.c |   27 ++
 11 files changed, 579 insertions(+), 547 deletions(-)

             reply	other threads:[~2016-03-24  1:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-24  1:25 Dan Williams [this message]
2016-03-24  1:25 ` [PATCH 01/13] libnvdimm, pfn: fix nvdimm_namespace_add_poison() vs section alignment Dan Williams
2016-03-24 10:10   ` Johannes Thumshirn
2016-03-24 14:48     ` 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=20160324012520.21436.22505.stgit@dwillia2-desk3.jf.intel.com \
    --to=dan.j.williams@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvdimm@lists.01.org \
    --cc=ross.zwisler@linux.intel.com \
    --cc=stable@vger.kernel.org \
    --cc=vishal.l.verma@intel.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