ext4: allow concurrent unaligned dio overwrites
RFC PATCH 1/1 ext4: allow concurrent unaligned dio overwrites
Hi all,
We've had a customer report a significant performance regression of sub-block (unaligned) direct writes between a couple distro kernels (that span a large range of upstream releases). I've not bisected upstream to narrow down to specific commit(s), but the regression appears to correspond with added concurrency restrictions of unaligned dio in ext4. Obviously this user should ideally move to a configuration that minimizes unaligned I/O, but while looking into this we also observed that XFS performs noticeably better with the same workload, even though it has the same general unaligned dio constraints.
The difference appears to be the use of IOMAP_DIO_OVERWRITE_ONLY in XFS, which allows optimistic concurrent submission of unaligned direct I/O under shared locking. I.e., if the dio turns out to be something other than a pure overwrite that may require block zeroing, iomap kicks the request back with -EAGAIN so it can be resubmitted with appropriate exclusivity.
I initially prototyped this same sort of logic on ext4, but on further inspection realized that ext4 seems to already check for dio overwrites in ext4_dio_write_checks(). Therefore ISTM that since ext4 already knows when a dio is purely overwrite, it can safely submit unaligned dios concurrently where it knows zeroing is not required, and then fall back to exclusive submission otherwise.
This RFC prototypes something along those lines using ilock_shared as a proxy for non-overwrite (since non-overwrite always means non-shared locking). Based on the following fio test against a prewritten (i.e. no unwritten extents) file, on an 8xcpu kvm guest, using default ext4 options:
fio --name=test --ioengine=libaio --direct=1 --group_reporting
--overwrite=1 --thread --size=10G --filename=/mnt/fio --readwrite=write --ramp_time=10s --runtime=60s --numjobs=8 --blocksize=2k --iodepth=256 --allow_file_create=0
... performance goes from something like ~1350 iops / 2.7 MB/s on a v6.1 kernel to +350k iops / +700MB/s on a patched v6.2.0-rc7 kernel. The latter is much more closely aligned to what I see from the same test against XFS.
This also survives an initial fstests regression run, though it does leave at least a couple open questions I can think of:
1. Do we care to be explicit about overwrites and perhaps plumb through an 'overwrite' flag from ext4_dio_write_checks()?
2. Do we want to use DIO_OVERWRITE_ONLY and assume iomap will never kick back an overwrite only I/O, or perhaps include retry logic similar to XFS? That may be superfluous, but it's not much additional code either.
Thoughts on any of this? If there's consensus I can followup with a v1 with a proper implementation, commit log, code comment updates, etc.
--- fs/ext4/file.c | 21 ++++++++++++--------- 1 file changed, 12 insertions(+), 9 deletions(-)
fs/ext4/file.c +12 -9
@@ -493,15 +493,14 @@ static ssize_t ext4_dio_write_iter(struct kiocb *iocb, struct iov_iter *from)const struct iomap_ops *iomap_ops = &ext4_iomap_ops;bool extend = false, unaligned_io = false;bool ilock_shared = true; +unsigned int dio_flags =0 ;/* * We initially start with shared inode lock unless it is * unaligned IO which needs exclusive lock anyways. */ -if (ext4_unaligned_io (inode, from, offset)) { +if (ext4_unaligned_io (inode, from, offset)) unaligned_io = true; - ilock_shared = false; - }/* * Quick check here without any i_rwsem lock to see if it is extending * IO. A more reliable check is done in ext4_dio_write_checks() with
@@ -563,9 +562,6 @@ static ssize_t ext4_dio_write_iter(struct kiocb *iocb, struct iov_iter *from)* below inode_dio_wait() may anyway become a no-op, since we start * with exclusive lock. */ -if (unaligned_io) -inode_dio_wait (inode); -if (extend) { handle =ext4_journal_start (inode,EXT4_HT_INODE ,2 );if (IS_ERR (handle)) {
@@ -582,11 +578,18 @@ static ssize_t ext4_dio_write_iter(struct kiocb *iocb, struct iov_iter *from)ext4_journal_stop (handle); } -if (ilock_shared) +if (ilock_shared) { iomap_ops = &ext4_iomap_overwrite_ops; +if (unaligned_io) + dio_flags =IOMAP_DIO_OVERWRITE_ONLY ; + }else if (unaligned_io || extend) { + dio_flags =IOMAP_DIO_FORCE_WAIT ; +if (unaligned_io) +inode_dio_wait (inode); + } ret =iomap_dio_rw (iocb, from, iomap_ops, &ext4_dio_write_ops, - (unaligned_io || extend) ?IOMAP_DIO_FORCE_WAIT :0 , -NULL ,0 ); + dio_flags,NULL ,0 ); +WARN_ON_ONCE (ret == -EAGAIN && !(iocb->ki_flags &IOCB_NOWAIT ));if (ret == -ENOTBLK ) ret =0 ;
Signature · 1 line
2.39.1
Ritesh Harjani
reviewerBrian Foster <[email protected]> writes:
Thanks for the patch.
Quoted 20 lines
Hi all,
We've had a customer report a significant performance regression of sub-block (unaligned) direct writes between a couple distro kernels (that span a large range of upstream releases). I've not bisected upstream to narrow down to specific commit(s), but the regression appears to correspond with added concurrency restrictions of unaligned dio in ext4. Obviously this user should ideally move to a configuration that minimizes unaligned I/O, but while looking into this we also observed that XFS performs noticeably better with the same workload, even though it has the same general unaligned dio constraints.
The difference appears to be the use of
IOMAP_DIO_OVERWRITE_ONLYin XFS, which allows optimistic concurrent submission of unaligned direct I/O under shared locking. I.e., if the dio turns out to be something other than a pure overwrite that may require block zeroing, iomap kicks the request back with-EAGAINso it can be resubmitted with appropriate exclusivity.
Quoted 6 lines
I initially prototyped this same sort of logic on ext4, but on further inspection realized that ext4 seems to already check for dio overwrites in
ext4_dio_write_checks(). Therefore ISTM that since ext4 already knows when a dio is purely overwrite, it can safely submit unaligned dios concurrently where it knows zeroing is not required, and then fall back to exclusive submission otherwise.
Yes, so in case of ext4, we start with a shared inode lock and check for extent mapping. If the entire length of the write is already mapped then we continue with ilock_shared. Otherwise we switch to exclusive locking.
So I think what you are proposing is that, in case of a unaligned write to a part which is already allocated and mapped, we don't need exclusive locking. That is because we don't need any allocation and neither partial blocks zeroing because it is not an unwritten extent.
Quick qn - what happens when two processes are writing to the same 4k block with 1k writes in parallel? Oh ok so inode_dio_wait() will protect this case.
Then yes, this does seems like it should work. Although I am not sure whether ext4 needs to use IOMAP_DIO_OVERWRITE_ONLY flag really?
This flag ends up setting IOMAP_OVERWRITE_ONLY flag again for lower layers of filesystem to make sure no block allocation/partial zeroing happens. XFS handles this, but ext4 as you mentioned does not require it. Hence I think we can drop the use of IOMAP_DIO_OVERWRITE_ONLY flag from ext4.
Quoted 71 lines
This RFC prototypes something along those lines using
ilock_sharedas a proxy for non-overwrite (since non-overwrite always means non-shared locking). Based on the following fio test against a prewritten (i.e. no unwritten extents) file, on an 8xcpu kvm guest, using default ext4 options:fio --name=test --ioengine=libaio --direct=1 --group_reporting
--overwrite=1 --thread --size=10G --filename=/mnt/fio --readwrite=write --ramp_time=10s --runtime=60s --numjobs=8 --blocksize=2k --iodepth=256 --allow_file_create=0... performance goes from something like ~1350 iops / 2.7 MB/s on a v6.1 kernel to +350k iops / +700MB/s on a patched v6.2.0-rc7 kernel. The latter is much more closely aligned to what I see from the same test against XFS.
This also survives an initial fstests regression run, though it does leave at least a couple open questions I can think of:
1. Do we care to be explicit about overwrites and perhaps plumb through an 'overwrite' flag from
ext4_dio_write_checks()?
2. Do we want to useDIO_OVERWRITE_ONLYand assume iomap will never kick back an overwrite only I/O, or perhaps include retry logic similar to XFS? That may be superfluous, but it's not much additional code either.Thoughts on any of this? If there's consensus I can followup with a v1 with a proper implementation, commit log, code comment updates, etc.
Not-Signed-off-by Brian Foster <[email protected]>--- fs/ext4/file.c | 21 ++++++++++++--------- 1 file changed, 12 insertions(+), 9 deletions(-)fs/ext4/file.c +2
-6@@ -493,15 +493,14 @@ static ssize_t ext4_dio_write_iter(struct kiocb *iocb, struct iov_iter *from)const struct iomap_ops *iomap_ops = &ext4_iomap_ops;bool extend = false, unaligned_io = false;bool ilock_shared = true; +unsigned int dio_flags =0 ;/* * We initially start with shared inode lock unless it is * unaligned IO which needs exclusive lock anyways. */ -if (ext4_unaligned_io (inode, from, offset)) { +if (ext4_unaligned_io (inode, from, offset)) unaligned_io = true; - ilock_shared = false; - }/* * Quick check here without any i_rwsem lock to see if it is extending * IO. A more reliable check is done in ext4_dio_write_checks() with @@ -563,9 +562,6 @@ static ssize_t ext4_dio_write_iter(struct kiocb *iocb, struct iov_iter *from)* below inode_dio_wait() may anyway become a no-op, since we start * with exclusive lock. */ -if (unaligned_io) -inode_dio_wait (inode); -if (extend) { handle =ext4_journal_start (inode,EXT4_HT_INODE ,2 );if (IS_ERR (handle)) {@@ -582,11 +578,18 @@ static ssize_t ext4_dio_write_iter(struct kiocb *iocb, struct iov_iter *from)ext4_journal_stop (handle); }
fs/ext4/file.c static ssize_t ext4_dio_write_iter(struct kiocb *iocb, struct iov_iter *from) · line 589
Quoted 10 lines
fs/ext4/file.c +8
-1-if (ilock_shared) +if (ilock_shared) { iomap_ops = &ext4_iomap_overwrite_ops; +if (unaligned_io) + dio_flags =IOMAP_DIO_OVERWRITE_ONLY ; + }else if (unaligned_io || extend) { + dio_flags =IOMAP_DIO_FORCE_WAIT ; +if (unaligned_io) +inode_dio_wait (inode); + }
This nested if logic has now become confusing, but I couldn't find anything easier either. It will be good though it this could be improved. Maybe if we add the unaligned_io logic in ext4_dio_write_checks(), it might make it easier to read?
-ritesh
Quoted 10 lines
fs/ext4/file.c +2
-3ret =iomap_dio_rw (iocb, from, iomap_ops, &ext4_dio_write_ops, - (unaligned_io || extend) ?IOMAP_DIO_FORCE_WAIT :0 , -NULL ,0 ); + dio_flags,NULL ,0 ); +WARN_ON_ONCE (ret == -EAGAIN && !(iocb->ki_flags &IOCB_NOWAIT ));if (ret == -ENOTBLK ) ret =0 ; --2.39.1
Quoted 4 lines · Ritesh Harjani
Brian Foster <[email protected]> writes:
Thanks for the patch.
Thanks for the feedback!
Quoted 27 lines
Quoted 20 lines
Hi all,
We've had a customer report a significant performance regression of sub-block (unaligned) direct writes between a couple distro kernels (that span a large range of upstream releases). I've not bisected upstream to narrow down to specific commit(s), but the regression appears to correspond with added concurrency restrictions of unaligned dio in ext4. Obviously this user should ideally move to a configuration that minimizes unaligned I/O, but while looking into this we also observed that XFS performs noticeably better with the same workload, even though it has the same general unaligned dio constraints.
The difference appears to be the use of
IOMAP_DIO_OVERWRITE_ONLYin XFS, which allows optimistic concurrent submission of unaligned direct I/O under shared locking. I.e., if the dio turns out to be something other than a pure overwrite that may require block zeroing, iomap kicks the request back with-EAGAINso it can be resubmitted with appropriate exclusivity.Quoted 6 lines
I initially prototyped this same sort of logic on ext4, but on further inspection realized that ext4 seems to already check for dio overwrites in
ext4_dio_write_checks(). Therefore ISTM that since ext4 already knows when a dio is purely overwrite, it can safely submit unaligned dios concurrently where it knows zeroing is not required, and then fall back to exclusive submission otherwise.
Quoted 9 lines
Yes, so in case of ext4, we start with a shared inode lock and check for extent mapping. If the entire length of the write is already mapped then we continue with
ilock_shared. Otherwise we switch to exclusive locking.So I think what you are proposing is that, in case of a unaligned write to a part which is already allocated and mapped, we don't need exclusive locking. That is because we don't need any allocation and neither partial blocks zeroing because it is not an unwritten extent.
Right.
Quoted 4 lines
Quick qn - what happens when two processes are writing to the same 4k block with 1k writes in parallel? Oh ok so
inode_dio_wait()will protect this case.
My understanding is that should work as normal so long as the blocks are mapped..? The key problem wrt to the locking/exclusivity is that for non-overwrite I/Os, any/all of the requests could do zeroing on the rest of the block and lead to corruption. This shouldn't happen if the writes are overwrites to mapped blocks, even if unaligned.
Quoted 3 lines
Then yes, this does seems like it should work. Although I am not sure whether ext4 needs to use
IOMAP_DIO_OVERWRITE_ONLYflag really?
Technically no I don't think it's needed. I originally thought the same sort of submit/retry logic that XFS uses would be necessary, then realized that the overwrite checking is already done before submission in ext4.
Quoted 6 lines
This flag ends up setting
IOMAP_OVERWRITE_ONLYflag again for lower layers of filesystem to make sure no block allocation/partial zeroing happens. XFS handles this, but ext4 as you mentioned does not require it. Hence I think we can drop the use ofIOMAP_DIO_OVERWRITE_ONLYflag from ext4.
Personally I think I would prefer to keep it out of caution, because it does instruct the iomap/dio layer that zeroing is unsafe if something happens to be wrong. The tradeoff is that if something unexpected happens, we'd see a spurious -EAGAIN failure from the dio rather than a submission that silently performs unsafe (but perhaps not corrupting) zeroing.
That said, I don't insist and defer to maintainers or whoever knows this code better. I'll keep the flag around prospectively until I get through more testing and review and drop it as a last step if that is ultimately preferred.
Quoted 71 lines
Quoted 71 lines
This RFC prototypes something along those lines using
ilock_sharedas a proxy for non-overwrite (since non-overwrite always means non-shared locking). Based on the following fio test against a prewritten (i.e. no unwritten extents) file, on an 8xcpu kvm guest, using default ext4 options:fio --name=test --ioengine=libaio --direct=1 --group_reporting
--overwrite=1 --thread --size=10G --filename=/mnt/fio --readwrite=write --ramp_time=10s --runtime=60s --numjobs=8 --blocksize=2k --iodepth=256 --allow_file_create=0... performance goes from something like ~1350 iops / 2.7 MB/s on a v6.1 kernel to +350k iops / +700MB/s on a patched v6.2.0-rc7 kernel. The latter is much more closely aligned to what I see from the same test against XFS.
This also survives an initial fstests regression run, though it does leave at least a couple open questions I can think of:
1. Do we care to be explicit about overwrites and perhaps plumb through an 'overwrite' flag from
ext4_dio_write_checks()?
2. Do we want to useDIO_OVERWRITE_ONLYand assume iomap will never kick back an overwrite only I/O, or perhaps include retry logic similar to XFS? That may be superfluous, but it's not much additional code either.Thoughts on any of this? If there's consensus I can followup with a v1 with a proper implementation, commit log, code comment updates, etc.
Not-Signed-off-by Brian Foster <[email protected]>--- fs/ext4/file.c | 21 ++++++++++++--------- 1 file changed, 12 insertions(+), 9 deletions(-)fs/ext4/file.c +2
-6@@ -493,15 +493,14 @@ static ssize_t ext4_dio_write_iter(struct kiocb *iocb, struct iov_iter *from)const struct iomap_ops *iomap_ops = &ext4_iomap_ops;bool extend = false, unaligned_io = false;bool ilock_shared = true; +unsigned int dio_flags =0 ;/* * We initially start with shared inode lock unless it is * unaligned IO which needs exclusive lock anyways. */ -if (ext4_unaligned_io (inode, from, offset)) { +if (ext4_unaligned_io (inode, from, offset)) unaligned_io = true; - ilock_shared = false; - }/* * Quick check here without any i_rwsem lock to see if it is extending * IO. A more reliable check is done in ext4_dio_write_checks() with @@ -563,9 +562,6 @@ static ssize_t ext4_dio_write_iter(struct kiocb *iocb, struct iov_iter *from)* below inode_dio_wait() may anyway become a no-op, since we start * with exclusive lock. */ -if (unaligned_io) -inode_dio_wait (inode); -if (extend) { handle =ext4_journal_start (inode,EXT4_HT_INODE ,2 );if (IS_ERR (handle)) {@@ -582,11 +578,18 @@ static ssize_t ext4_dio_write_iter(struct kiocb *iocb, struct iov_iter *from)ext4_journal_stop (handle); }
Quoted 16 lines
fs/ext4/file.c static ssize_t ext4_dio_write_iter(struct kiocb *iocb, struct iov_iter *from) · line 589
Quoted 10 lines
fs/ext4/file.c +8
-1-if (ilock_shared) +if (ilock_shared) { iomap_ops = &ext4_iomap_overwrite_ops; +if (unaligned_io) + dio_flags =IOMAP_DIO_OVERWRITE_ONLY ; + }else if (unaligned_io || extend) { + dio_flags =IOMAP_DIO_FORCE_WAIT ; +if (unaligned_io) +inode_dio_wait (inode); + }This nested if logic has now become confusing, but I couldn't find anything easier either. It will be good though it this could be improved. Maybe if we add the
unaligned_iologic inext4_dio_write_checks(), it might make it easier to read?
Yeah, I reshuffled the logic around a couple different ways that ultimately didn't look much different. I was thinking about adding an overwrite flag, but I can also try relocating the unaligned check and see if that brings about ideas for anything nicer..
Brian
Quoted 14 lines
-ritesh
Quoted 10 lines
fs/ext4/file.c +2
-3ret =iomap_dio_rw (iocb, from, iomap_ops, &ext4_dio_write_ops, - (unaligned_io || extend) ?IOMAP_DIO_FORCE_WAIT :0 , -NULL ,0 ); + dio_flags,NULL ,0 ); +WARN_ON_ONCE (ret == -EAGAIN && !(iocb->ki_flags &IOCB_NOWAIT ));if (ret == -ENOTBLK ) ret =0 ; --2.39.1