From: Christoph Hellwig <hch@lst.de>
To: xfs@oss.sgi.com
Subject: [PATCH 1/6] iomap: support DAX based zeroing
Date: Tue, 12 Apr 2016 15:26:48 -0700 [thread overview]
Message-ID: <1460500013-28334-2-git-send-email-hch@lst.de> (raw)
In-Reply-To: <1460500013-28334-1-git-send-email-hch@lst.de>
This avoid needing a separate inefficient get_block based DAX zero_range
implementation in file systems.
Signed-off-by: Christoph Hellwig <hch@lst.de>
---
fs/iomap.c | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/fs/iomap.c b/fs/iomap.c
index 28a8fcb..a3e7dea 100644
--- a/fs/iomap.c
+++ b/fs/iomap.c
@@ -24,6 +24,7 @@
#include <linux/uio.h>
#include <linux/backing-dev.h>
#include <linux/buffer_head.h>
+#include <linux/dax.h>
#include "internal.h"
typedef loff_t (*iomap_actor_t)(struct inode *inode, loff_t pos, loff_t len,
@@ -264,6 +265,15 @@ iomap_zero_range_actor(struct inode *inode, loff_t pos, loff_t count,
if (iomap->type == IOMAP_HOLE || iomap->type == IOMAP_UNWRITTEN)
return count;
+#ifdef CONFIG_FS_DAX
+ if (IS_DAX(inode)) {
+ status = dax_clear_sectors(iomap->bdev, iomap->blkno, count);
+ if (status)
+ return status;
+ return count;
+ }
+#endif
+
do {
unsigned offset, bytes;
--
2.1.4
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2016-04-12 22:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 22:26 RFC: use iomap infrastructure for all our zeroing needs Christoph Hellwig
2016-04-12 22:26 ` Christoph Hellwig [this message]
2016-04-12 22:26 ` [PATCH 2/6] xfs: use iomap infrastructure for DAX zeroing Christoph Hellwig
2016-04-12 22:26 ` [PATCH 3/6] xfs: handle 64-bit length in xfs_iozero Christoph Hellwig
2016-04-12 22:26 ` [PATCH 4/6] xfs: use xfs_zero_range in xfs_zero_eof Christoph Hellwig
2016-04-12 22:26 ` [PATCH 5/6] xfs: split xfs_free_file_space in manageable pieces Christoph Hellwig
2016-04-12 22:26 ` [PATCH 6/6] kill xfs_zero_remaining_bytes Christoph Hellwig
2016-04-13 21:55 ` RFC: use iomap infrastructure for all our zeroing needs Dave Chinner
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=1460500013-28334-2-git-send-email-hch@lst.de \
--to=hch@lst.de \
--cc=xfs@oss.sgi.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