From: Matthew Wilcox <matthew.r.wilcox@intel.com>
To: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Cc: Matthew Wilcox <willy@linux.intel.com>,
Matthew Wilcox <matthew.r.wilcox@intel.com>
Subject: [PATCH v9 22/22] brd: Rename XIP to DAX
Date: Fri, 1 Aug 2014 09:27:38 -0400 [thread overview]
Message-ID: <909c355806cfd84e705856ee01f8c8ae4b5f73ca.1406897885.git.willy@linux.intel.com> (raw)
In-Reply-To: <cover.1406897885.git.willy@linux.intel.com>
In-Reply-To: <cover.1406897885.git.willy@linux.intel.com>
From: Matthew Wilcox <willy@linux.intel.com>
Since this is relating to FS_XIP, not KERNEL_XIP, it should be called
DAX instead of XIP.
Signed-off-by: Matthew Wilcox <matthew.r.wilcox@intel.com>
---
drivers/block/Kconfig | 13 +++++++------
drivers/block/brd.c | 14 +++++++-------
fs/Kconfig | 4 ++--
3 files changed, 16 insertions(+), 15 deletions(-)
diff --git a/drivers/block/Kconfig b/drivers/block/Kconfig
index 014a1cf..1b8094d 100644
--- a/drivers/block/Kconfig
+++ b/drivers/block/Kconfig
@@ -393,14 +393,15 @@ config BLK_DEV_RAM_SIZE
The default value is 4096 kilobytes. Only change this if you know
what you are doing.
-config BLK_DEV_XIP
- bool "Support XIP filesystems on RAM block device"
- depends on BLK_DEV_RAM
+config BLK_DEV_RAM_DAX
+ bool "Support Direct Access (DAX) to RAM block devices"
+ depends on BLK_DEV_RAM && FS_DAX
default n
help
- Support XIP filesystems (such as ext2 with XIP support on) on
- top of block ram device. This will slightly enlarge the kernel, and
- will prevent RAM block device backing store memory from being
+ Support filesystems using DAX to access RAM block devices. This
+ avoids double-buffering data in the page cache before copying it
+ to the block device. Answering Y will slightly enlarge the kernel,
+ and will prevent RAM block device backing store memory from being
allocated from highmem (only a problem for highmem systems).
config CDROM_PKTCDVD
diff --git a/drivers/block/brd.c b/drivers/block/brd.c
index a10a0a9..3483458 100644
--- a/drivers/block/brd.c
+++ b/drivers/block/brd.c
@@ -97,13 +97,13 @@ static struct page *brd_insert_page(struct brd_device *brd, sector_t sector)
* Must use NOIO because we don't want to recurse back into the
* block or filesystem layers from page reclaim.
*
- * Cannot support XIP and highmem, because our ->direct_access
- * routine for XIP must return memory that is always addressable.
- * If XIP was reworked to use pfns and kmap throughout, this
+ * Cannot support DAX and highmem, because our ->direct_access
+ * routine for DAX must return memory that is always addressable.
+ * If DAX was reworked to use pfns and kmap throughout, this
* restriction might be able to be lifted.
*/
gfp_flags = GFP_NOIO | __GFP_ZERO;
-#ifndef CONFIG_BLK_DEV_XIP
+#ifndef CONFIG_BLK_DEV_RAM_DAX
gfp_flags |= __GFP_HIGHMEM;
#endif
page = alloc_page(gfp_flags);
@@ -369,7 +369,7 @@ static int brd_rw_page(struct block_device *bdev, sector_t sector,
return err;
}
-#ifdef CONFIG_BLK_DEV_XIP
+#ifdef CONFIG_BLK_DEV_RAM_DAX
static long brd_direct_access(struct block_device *bdev, sector_t sector,
void **kaddr, unsigned long *pfn, long size)
{
@@ -388,6 +388,8 @@ static long brd_direct_access(struct block_device *bdev, sector_t sector,
* file is mapped to the next page of physical RAM */
return min_t(long, PAGE_SIZE, size);
}
+#else
+#define brd_direct_access NULL
#endif
static int brd_ioctl(struct block_device *bdev, fmode_t mode,
@@ -428,9 +430,7 @@ static const struct block_device_operations brd_fops = {
.owner = THIS_MODULE,
.rw_page = brd_rw_page,
.ioctl = brd_ioctl,
-#ifdef CONFIG_BLK_DEV_XIP
.direct_access = brd_direct_access,
-#endif
};
/*
diff --git a/fs/Kconfig b/fs/Kconfig
index a9eb53d..117900f 100644
--- a/fs/Kconfig
+++ b/fs/Kconfig
@@ -34,7 +34,7 @@ source "fs/btrfs/Kconfig"
source "fs/nilfs2/Kconfig"
config FS_DAX
- bool "Direct Access support"
+ bool "Direct Access (DAX) support"
depends on MMU
help
Direct Access (DAX) can be used on memory-backed block devices.
@@ -45,7 +45,7 @@ config FS_DAX
If you do not have a block device that is capable of using this,
or if unsure, say N. Saying Y will increase the size of the kernel
- by about 2kB.
+ by about 5kB.
endif # BLOCK
--
2.0.1
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2014-08-01 13:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 13:27 [PATCH v9 00/22] Support ext4 on NV-DIMMs Matthew Wilcox
2014-08-01 13:27 ` [PATCH v9 01/22] axonram: Fix bug in direct_access Matthew Wilcox
2014-08-01 13:27 ` [PATCH v9 02/22] Change direct_access calling convention Matthew Wilcox
2014-08-01 13:27 ` [PATCH v9 03/22] Fix XIP fault vs truncate race Matthew Wilcox
2014-08-01 13:27 ` [PATCH v9 04/22] Allow page fault handlers to perform the COW Matthew Wilcox
2014-08-01 13:27 ` [PATCH v9 05/22] Introduce IS_DAX(inode) Matthew Wilcox
2014-08-01 13:27 ` [PATCH v9 06/22] Add copy_to_iter(), copy_from_iter() and iov_iter_zero() Matthew Wilcox
2014-08-01 13:27 ` [PATCH v9 07/22] Replace XIP read and write with DAX I/O Matthew Wilcox
2014-08-01 13:27 ` [PATCH v9 08/22] Replace ext2_clear_xip_target with dax_clear_blocks Matthew Wilcox
2014-08-01 13:27 ` [PATCH v9 09/22] Replace the XIP page fault handler with the DAX page fault handler Matthew Wilcox
2014-08-01 13:27 ` [PATCH v9 10/22] Replace xip_truncate_page with dax_truncate_page Matthew Wilcox
2014-08-01 13:27 ` [PATCH v9 11/22] Replace XIP documentation with DAX documentation Matthew Wilcox
2014-08-01 13:27 ` [PATCH v9 12/22] Remove get_xip_mem Matthew Wilcox
2014-08-01 13:27 ` [PATCH v9 13/22] ext2: Remove ext2_xip_verify_sb() Matthew Wilcox
2014-08-01 13:27 ` [PATCH v9 14/22] ext2: Remove ext2_use_xip Matthew Wilcox
2014-08-01 13:27 ` [PATCH v9 15/22] ext2: Remove xip.c and xip.h Matthew Wilcox
2014-08-01 13:27 ` [PATCH v9 16/22] Remove CONFIG_EXT2_FS_XIP and rename CONFIG_FS_XIP to CONFIG_FS_DAX Matthew Wilcox
2014-08-01 13:27 ` [PATCH v9 17/22] ext2: Remove ext2_aops_xip Matthew Wilcox
2014-08-01 13:27 ` [PATCH v9 18/22] Get rid of most mentions of XIP in ext2 Matthew Wilcox
2014-08-01 13:27 ` [PATCH v9 19/22] xip: Add xip_zero_page_range Matthew Wilcox
2014-08-01 13:27 ` [PATCH v9 20/22] ext4: Avoid lock inversion between i_mmap_mutex and transaction start Matthew Wilcox
2014-08-01 13:27 ` [PATCH v9 21/22] ext4: Add DAX functionality Matthew Wilcox
2014-08-01 13:27 ` Matthew Wilcox [this message]
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=909c355806cfd84e705856ee01f8c8ae4b5f73ca.1406897885.git.willy@linux.intel.com \
--to=matthew.r.wilcox@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=willy@linux.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