From: Dan Williams <dan.j.williams@intel.com>
To: linux-nvdimm@lists.01.org
Cc: jack@suse.cz, snitzer@redhat.com,
Heiko Carstens <heiko.carstens@de.ibm.com>,
david@fromorbit.com, linux-kernel@vger.kernel.org,
linux-xfs@vger.kernel.org,
Bart Van Assche <Bart.VanAssche@wdc.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
linux-fsdevel@vger.kernel.org, hch@lst.de
Subject: [PATCH v8 08/18] dax: introduce CONFIG_DAX_DRIVER
Date: Fri, 30 Mar 2018 21:02:52 -0700 [thread overview]
Message-ID: <152246897244.36038.14718237765737542802.stgit@dwillia2-desk3.amr.corp.intel.com> (raw)
In-Reply-To: <152246892890.36038.18436540150980653229.stgit@dwillia2-desk3.amr.corp.intel.com>
In support of allowing device-mapper to compile out idle/dead code when
there are no dax providers in the system, introduce the DAX_DRIVER
symbol. This is selected by all leaf drivers that device-mapper might be
layered on top. This allows device-mapper to conditionally 'select DAX'
only when a provider is present.
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
Reported-by: Bart Van Assche <Bart.VanAssche@wdc.com>
Reviewed-by: Mike Snitzer <snitzer@redhat.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
---
drivers/dax/Kconfig | 5 ++++-
drivers/nvdimm/Kconfig | 2 +-
drivers/s390/block/Kconfig | 2 +-
3 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/drivers/dax/Kconfig b/drivers/dax/Kconfig
index b79aa8f7a497..e0700bf4893a 100644
--- a/drivers/dax/Kconfig
+++ b/drivers/dax/Kconfig
@@ -1,3 +1,7 @@
+config DAX_DRIVER
+ select DAX
+ bool
+
menuconfig DAX
tristate "DAX: direct access to differentiated memory"
select SRCU
@@ -16,7 +20,6 @@ config DEV_DAX
baseline memory pool. Mappings of a /dev/daxX.Y device impose
restrictions that make the mapping behavior deterministic.
-
config DEV_DAX_PMEM
tristate "PMEM DAX: direct access to persistent memory"
depends on LIBNVDIMM && NVDIMM_DAX && DEV_DAX
diff --git a/drivers/nvdimm/Kconfig b/drivers/nvdimm/Kconfig
index a65f2e1d9f53..40cbdb16e23e 100644
--- a/drivers/nvdimm/Kconfig
+++ b/drivers/nvdimm/Kconfig
@@ -20,7 +20,7 @@ if LIBNVDIMM
config BLK_DEV_PMEM
tristate "PMEM: Persistent memory block device support"
default LIBNVDIMM
- select DAX
+ select DAX_DRIVER
select ND_BTT if BTT
select ND_PFN if NVDIMM_PFN
help
diff --git a/drivers/s390/block/Kconfig b/drivers/s390/block/Kconfig
index 1444333210c7..9ac7574e3cfb 100644
--- a/drivers/s390/block/Kconfig
+++ b/drivers/s390/block/Kconfig
@@ -15,8 +15,8 @@ config BLK_DEV_XPRAM
config DCSSBLK
def_tristate m
- select DAX
select FS_DAX_LIMITED
+ select DAX_DRIVER
prompt "DCSSBLK support"
depends on S390 && BLOCK
help
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
WARNING: multiple messages have this Message-ID (diff)
From: Dan Williams <dan.j.williams@intel.com>
To: linux-nvdimm@lists.01.org
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Bart Van Assche <Bart.VanAssche@wdc.com>,
Mike Snitzer <snitzer@redhat.com>,
david@fromorbit.com, hch@lst.de, linux-fsdevel@vger.kernel.org,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
jack@suse.cz, snitzer@redhat.com
Subject: [PATCH v8 08/18] dax: introduce CONFIG_DAX_DRIVER
Date: Fri, 30 Mar 2018 21:02:52 -0700 [thread overview]
Message-ID: <152246897244.36038.14718237765737542802.stgit@dwillia2-desk3.amr.corp.intel.com> (raw)
In-Reply-To: <152246892890.36038.18436540150980653229.stgit@dwillia2-desk3.amr.corp.intel.com>
In support of allowing device-mapper to compile out idle/dead code when
there are no dax providers in the system, introduce the DAX_DRIVER
symbol. This is selected by all leaf drivers that device-mapper might be
layered on top. This allows device-mapper to conditionally 'select DAX'
only when a provider is present.
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
Reported-by: Bart Van Assche <Bart.VanAssche@wdc.com>
Reviewed-by: Mike Snitzer <snitzer@redhat.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
---
drivers/dax/Kconfig | 5 ++++-
drivers/nvdimm/Kconfig | 2 +-
drivers/s390/block/Kconfig | 2 +-
3 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/drivers/dax/Kconfig b/drivers/dax/Kconfig
index b79aa8f7a497..e0700bf4893a 100644
--- a/drivers/dax/Kconfig
+++ b/drivers/dax/Kconfig
@@ -1,3 +1,7 @@
+config DAX_DRIVER
+ select DAX
+ bool
+
menuconfig DAX
tristate "DAX: direct access to differentiated memory"
select SRCU
@@ -16,7 +20,6 @@ config DEV_DAX
baseline memory pool. Mappings of a /dev/daxX.Y device impose
restrictions that make the mapping behavior deterministic.
-
config DEV_DAX_PMEM
tristate "PMEM DAX: direct access to persistent memory"
depends on LIBNVDIMM && NVDIMM_DAX && DEV_DAX
diff --git a/drivers/nvdimm/Kconfig b/drivers/nvdimm/Kconfig
index a65f2e1d9f53..40cbdb16e23e 100644
--- a/drivers/nvdimm/Kconfig
+++ b/drivers/nvdimm/Kconfig
@@ -20,7 +20,7 @@ if LIBNVDIMM
config BLK_DEV_PMEM
tristate "PMEM: Persistent memory block device support"
default LIBNVDIMM
- select DAX
+ select DAX_DRIVER
select ND_BTT if BTT
select ND_PFN if NVDIMM_PFN
help
diff --git a/drivers/s390/block/Kconfig b/drivers/s390/block/Kconfig
index 1444333210c7..9ac7574e3cfb 100644
--- a/drivers/s390/block/Kconfig
+++ b/drivers/s390/block/Kconfig
@@ -15,8 +15,8 @@ config BLK_DEV_XPRAM
config DCSSBLK
def_tristate m
- select DAX
select FS_DAX_LIMITED
+ select DAX_DRIVER
prompt "DCSSBLK support"
depends on S390 && BLOCK
help
WARNING: multiple messages have this Message-ID (diff)
From: Dan Williams <dan.j.williams@intel.com>
To: linux-nvdimm@lists.01.org
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Bart Van Assche <Bart.VanAssche@wdc.com>,
Mike Snitzer <snitzer@redhat.com>,
david@fromorbit.com, hch@lst.de, linux-fsdevel@vger.kernel.org,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
jack@suse.czsnitzer@redhat.com
Subject: [PATCH v8 08/18] dax: introduce CONFIG_DAX_DRIVER
Date: Fri, 30 Mar 2018 21:02:52 -0700 [thread overview]
Message-ID: <152246897244.36038.14718237765737542802.stgit@dwillia2-desk3.amr.corp.intel.com> (raw)
In-Reply-To: <152246892890.36038.18436540150980653229.stgit@dwillia2-desk3.amr.corp.intel.com>
In support of allowing device-mapper to compile out idle/dead code when
there are no dax providers in the system, introduce the DAX_DRIVER
symbol. This is selected by all leaf drivers that device-mapper might be
layered on top. This allows device-mapper to conditionally 'select DAX'
only when a provider is present.
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
Reported-by: Bart Van Assche <Bart.VanAssche@wdc.com>
Reviewed-by: Mike Snitzer <snitzer@redhat.com>
Signed-off-by: Dan Williams <dan.j.williams@intel.com>
---
drivers/dax/Kconfig | 5 ++++-
drivers/nvdimm/Kconfig | 2 +-
drivers/s390/block/Kconfig | 2 +-
3 files changed, 6 insertions(+), 3 deletions(-)
diff --git a/drivers/dax/Kconfig b/drivers/dax/Kconfig
index b79aa8f7a497..e0700bf4893a 100644
--- a/drivers/dax/Kconfig
+++ b/drivers/dax/Kconfig
@@ -1,3 +1,7 @@
+config DAX_DRIVER
+ select DAX
+ bool
+
menuconfig DAX
tristate "DAX: direct access to differentiated memory"
select SRCU
@@ -16,7 +20,6 @@ config DEV_DAX
baseline memory pool. Mappings of a /dev/daxX.Y device impose
restrictions that make the mapping behavior deterministic.
-
config DEV_DAX_PMEM
tristate "PMEM DAX: direct access to persistent memory"
depends on LIBNVDIMM && NVDIMM_DAX && DEV_DAX
diff --git a/drivers/nvdimm/Kconfig b/drivers/nvdimm/Kconfig
index a65f2e1d9f53..40cbdb16e23e 100644
--- a/drivers/nvdimm/Kconfig
+++ b/drivers/nvdimm/Kconfig
@@ -20,7 +20,7 @@ if LIBNVDIMM
config BLK_DEV_PMEM
tristate "PMEM: Persistent memory block device support"
default LIBNVDIMM
- select DAX
+ select DAX_DRIVER
select ND_BTT if BTT
select ND_PFN if NVDIMM_PFN
help
diff --git a/drivers/s390/block/Kconfig b/drivers/s390/block/Kconfig
index 1444333210c7..9ac7574e3cfb 100644
--- a/drivers/s390/block/Kconfig
+++ b/drivers/s390/block/Kconfig
@@ -15,8 +15,8 @@ config BLK_DEV_XPRAM
config DCSSBLK
def_tristate m
- select DAX
select FS_DAX_LIMITED
+ select DAX_DRIVER
prompt "DCSSBLK support"
depends on S390 && BLOCK
help
next prev parent reply other threads:[~2018-03-31 4:12 UTC|newest]
Thread overview: 111+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-31 4:02 [PATCH v8 00/18] dax: fix dma vs truncate/hole-punch Dan Williams
2018-03-31 4:02 ` Dan Williams
2018-03-31 4:02 ` Dan Williams
2018-03-31 4:02 ` Dan Williams
2018-03-31 4:02 ` [PATCH v8 01/18] dax: store pfns in the radix Dan Williams
2018-03-31 4:02 ` Dan Williams
2018-03-31 4:02 ` Dan Williams
2018-03-31 4:02 ` [PATCH v8 02/18] fs, dax: prepare for dax-specific address_space_operations Dan Williams
2018-03-31 4:02 ` Dan Williams
2018-03-31 4:02 ` Dan Williams
2018-03-31 4:02 ` [PATCH v8 03/18] block, dax: remove dead code in blkdev_writepages() Dan Williams
2018-03-31 4:02 ` Dan Williams
2018-03-31 4:02 ` Dan Williams
2018-03-31 4:02 ` [PATCH v8 04/18] xfs, dax: introduce xfs_dax_aops Dan Williams
2018-03-31 4:02 ` Dan Williams
2018-03-31 4:02 ` Dan Williams
2018-03-31 4:02 ` [PATCH v8 05/18] ext4, dax: introduce ext4_dax_aops Dan Williams
2018-03-31 4:02 ` Dan Williams
2018-03-31 4:02 ` Dan Williams
2018-03-31 4:02 ` Dan Williams
2018-04-03 11:50 ` Jan Kara
2018-04-03 11:50 ` Jan Kara
2018-04-03 11:50 ` Jan Kara
2018-03-31 4:02 ` [PATCH v8 06/18] ext2, dax: introduce ext2_dax_aops Dan Williams
2018-03-31 4:02 ` Dan Williams
2018-04-03 11:51 ` Jan Kara
2018-04-03 11:51 ` Jan Kara
2018-03-31 4:02 ` [PATCH v8 07/18] fs, dax: use page->mapping to warn if truncate collides with a busy page Dan Williams
2018-03-31 4:02 ` Dan Williams
2018-03-31 4:02 ` Dan Williams
2018-03-31 4:02 ` Dan Williams [this message]
2018-03-31 4:02 ` [PATCH v8 08/18] dax: introduce CONFIG_DAX_DRIVER Dan Williams
2018-03-31 4:02 ` Dan Williams
2018-03-31 4:02 ` [PATCH v8 09/18] dax, dm: allow device-mapper to operate without dax support Dan Williams
2018-03-31 4:02 ` Dan Williams
2018-03-31 4:02 ` Dan Williams
2018-03-31 4:03 ` [PATCH v8 10/18] dax, dm: introduce ->fs_{claim, release}() dax_device infrastructure Dan Williams
2018-03-31 4:03 ` Dan Williams
2018-03-31 4:03 ` Dan Williams
2018-04-03 18:24 ` Dan Williams
2018-04-03 18:24 ` Dan Williams
2018-04-03 19:39 ` Mike Snitzer
2018-04-03 19:39 ` Mike Snitzer
2018-04-03 19:47 ` Dan Williams
2018-04-03 19:47 ` Dan Williams
2018-04-03 20:36 ` [PATCH v9] " Dan Williams
2018-04-03 20:36 ` Dan Williams
2018-04-03 20:36 ` Dan Williams
2018-04-03 21:13 ` Mike Snitzer
2018-04-03 21:13 ` Mike Snitzer
2018-04-03 21:13 ` Mike Snitzer
2018-03-31 4:03 ` [PATCH v8 11/18] mm, dax: enable filesystems to trigger dev_pagemap ->page_free callbacks Dan Williams
2018-03-31 4:03 ` Dan Williams
2018-03-31 4:03 ` Dan Williams
2018-04-04 21:23 ` [v8, " Andrei Vagin
2018-04-04 21:23 ` Andrei Vagin
2018-04-04 21:27 ` Dan Williams
2018-04-04 21:27 ` Dan Williams
2018-04-04 21:35 ` Dan Williams
2018-04-04 21:35 ` Dan Williams
2018-04-04 23:19 ` Stephen Rothwell
2018-04-04 21:40 ` Andrei Vagin
2018-04-04 21:40 ` Andrei Vagin
2018-03-31 4:03 ` [PATCH v8 12/18] memremap: split devm_memremap_pages() and memremap() infrastructure Dan Williams
2018-03-31 4:03 ` Dan Williams
2018-03-31 4:03 ` Dan Williams
2018-03-31 4:03 ` [PATCH v8 13/18] mm, dev_pagemap: introduce CONFIG_DEV_PAGEMAP_OPS Dan Williams
2018-03-31 4:03 ` Dan Williams
2018-03-31 4:03 ` Dan Williams
2018-03-31 4:03 ` [PATCH v8 14/18] memremap: mark devm_memremap_pages() EXPORT_SYMBOL_GPL Dan Williams
2018-03-31 4:03 ` Dan Williams
2018-03-31 4:03 ` [PATCH v8 15/18] mm, fs, dax: handle layout changes to pinned dax mappings Dan Williams
2018-03-31 4:03 ` Dan Williams
2018-03-31 4:03 ` Dan Williams
2018-04-04 9:46 ` Jan Kara
2018-04-04 9:46 ` Jan Kara
2018-04-04 10:06 ` Jan Kara
2018-04-04 10:06 ` Jan Kara
2018-04-04 14:12 ` Dan Williams
2018-04-04 14:12 ` Dan Williams
2018-04-07 19:38 ` Dan Williams
2018-04-07 19:38 ` Dan Williams
2018-04-08 3:11 ` Paul E. McKenney
2018-04-08 3:11 ` Paul E. McKenney
2018-04-09 16:39 ` Jan Kara
2018-04-09 16:39 ` Jan Kara
2018-04-09 18:14 ` Paul E. McKenney
2018-04-09 18:14 ` Paul E. McKenney
2018-04-09 16:49 ` Jan Kara
2018-04-09 16:49 ` Jan Kara
2018-04-09 16:51 ` Dan Williams
2018-04-09 16:51 ` Dan Williams
2018-04-13 22:03 ` Dan Williams
2018-04-13 22:03 ` Dan Williams
2018-04-13 22:48 ` Paul E. McKenney
2018-04-13 22:48 ` Paul E. McKenney
2018-04-19 10:44 ` Jan Kara
2018-04-19 10:44 ` Jan Kara
2018-04-20 3:00 ` Dan Williams
2018-04-20 3:00 ` Dan Williams
2018-03-31 4:03 ` [PATCH v8 16/18] xfs: prepare xfs_break_layouts() to be called with XFS_MMAPLOCK_EXCL Dan Williams
2018-03-31 4:03 ` Dan Williams
2018-03-31 4:03 ` Dan Williams
2018-03-31 4:03 ` [PATCH v8 17/18] xfs: prepare xfs_break_layouts() for another layout type Dan Williams
2018-03-31 4:03 ` Dan Williams
2018-03-31 4:03 ` Dan Williams
2018-03-31 4:03 ` [PATCH v8 18/18] xfs, dax: introduce xfs_break_dax_layouts() Dan Williams
2018-03-31 4:03 ` Dan Williams
2018-03-31 4:03 ` Dan Williams
2018-04-04 9:55 ` Jan Kara
2018-04-04 9:55 ` 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=152246897244.36038.14718237765737542802.stgit@dwillia2-desk3.amr.corp.intel.com \
--to=dan.j.williams@intel.com \
--cc=Bart.VanAssche@wdc.com \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=heiko.carstens@de.ibm.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=linux-xfs@vger.kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=snitzer@redhat.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 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.