From: Eric Sandeen <sandeen@redhat.com>
To: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
Jan Kara <jack@suse.cz>
Subject: [PATCH] ext4: don't unconditionally zero blocks on dax writes
Date: Wed, 20 Sep 2017 16:44:44 -0500 [thread overview]
Message-ID: <51f1e5a8-0276-5963-afba-b10c6e194b52@redhat.com> (raw)
The conversion to iomap seems to have lost the ability to
conditionally /not/ prezero dax blocks. This leads to
double writes which cuts throughput in half in some
cases.
This puts back the old conditional zeroing logic.
Signed-off-by: Eric Sandeen <sandeen@redhat.com>
---
I might be completely missing something here, i.e. whether
the change may have been intentional, etc. The patch is
only lightly tested but a which check here seems to DTRT.
Thanks,
-Eric
diff --git a/fs/ext4/inode.c b/fs/ext4/inode.c
index c774bdc..9179a59 100644
--- a/fs/ext4/inode.c
+++ b/fs/ext4/inode.c
@@ -3423,6 +3423,7 @@ static int ext4_iomap_begin(struct inode *inode, loff_t offset, loff_t length,
int dio_credits;
handle_t *handle;
int retries = 0;
+ int flags;
/* Trim mapping request to maximum we can map at once for DIO */
if (map.m_len > DIO_MAX_BLOCKS)
@@ -3440,8 +3441,16 @@ static int ext4_iomap_begin(struct inode *inode, loff_t offset, loff_t length,
if (IS_ERR(handle))
return PTR_ERR(handle);
- ret = ext4_map_blocks(handle, inode, &map,
- EXT4_GET_BLOCKS_CREATE_ZERO);
+ /*
+ * We can avoid zeroing for aligned DAX writes beyond EOF. Other
+ * writes need zeroing either because they can race with page
+ * faults or because they use partial blocks.
+ */
+ flags = EXT4_GET_BLOCKS_PRE_IO | EXT4_GET_BLOCKS_CREATE;
+ if (round_down(offset, 1<<inode->i_blkbits) < inode->i_size ||
+ !ext4_aligned_io(inode, offset, length))
+ flags |= EXT4_GET_BLOCKS_ZERO;
+ ret = ext4_map_blocks(handle, inode, &map, flags);
if (ret < 0) {
ext4_journal_stop(handle);
if (ret == -ENOSPC &&
next reply other threads:[~2017-09-20 21:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-20 21:44 Eric Sandeen [this message]
2017-09-20 22:37 ` [PATCH] ext4: don't unconditionally zero blocks on dax writes Eric Sandeen
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=51f1e5a8-0276-5963-afba-b10c6e194b52@redhat.com \
--to=sandeen@redhat.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).