ext4: port direct I/O to iomap infrastructure
Subsystems (4)
v4 cover ext4: port direct I/O to iomap infrastructure
This patch series ports the ext4 direct I/O paths over to the iomap infrastructure. The legacy buffer_head based direct I/O paths have subsequently been removed as they're no longer in use. The result of this change is that ext4 now uses the newer iomap framework for direct I/O operations, which results in an overall cleaner implementation and keeps the code isolated from buffer_head internals. In addition to this, a slight performance boost may be expected while using O_SYNC | O_DIRECT I/O.
The changes within this patch series have been tested via xfstests in both DAX and non-DAX modes using the various filesystem configuration options i.e. 4k, dioread_nolock, etc.
Changes since v3:
- Introduced a couple preparation patches around refactoring the ext4 iomap code. This involved splitting chunks of the existing ->iomap_begin() callback into separate helpers.
- Moved out the orphan handling code into a higher level caller. It used to be within ext4_iomap_begin(), but is now within ext4_dio_write_iter() and similarily ext4_dax_write_iter().
- Renamed the helper function from ext4_dio_checks() to ext4_dio_supported(). Overall, it just reads better when using this helper throughout the code.
- Cleaned up the ->end_io() handler. This was a result of refactoring ext4_handle_inode_extension() and allowing it to perform clean up routines for extension cases rather than calling ext4_handle_failed_inode_extension() explicitly.
- Added a couple comments here and there to bits of logic that aren't immediately obvious.
- Rather than having the clean up code in a separate patch at the end of the series, I've incorporated the clean up into the patches directly.
Thank you to all that took the time to review the patch series and provide very valuable feedback. This includes Jan Kara, Christoph Hellwig, Ritesh Harjani, and anybody else that I may have missed.
Matthew Bobrowski (8):
ext4: move out iomap field population into separate helper
ext4: move out IOMAP_WRITE path into separate helper
ext4: introduce new callback for IOMAP_REPORT operations
ext4: introduce direct I/O read path using iomap infrastructure
ext4: move inode extension/truncate code out from ->iomap_end()
callback
ext4: move inode extension checks out from ext4_iomap_alloc()
ext4: reorder map.m_flags checks in ext4_set_iomap()
ext4: introduce direct I/O write path using iomap infrastructure
fs/ext4/ext4.h | 4 +- fs/ext4/extents.c | 11 +- fs/ext4/file.c | 387 ++++++++++++++++++++----- fs/ext4/inode.c | 709 +++++++++++----------------------------------- 4 files changed, 484 insertions(+), 627 deletions(-)
Signature · 1 line
2.20.1
PATCH v4 1/8 ext4: move out iomap field population into separate helper
Separate the iomap field population chunk into a separate simple helper routine. This helps reducing the overall clutter within the ext4_iomap_begin() callback, especially as we move across more code to make use of iomap infrastructure.
--- fs/ext4/inode.c | 65 ++++++++++++++++++++++++++++--------------------- 1 file changed, 37 insertions(+), 28 deletions(-)
fs/ext4/inode.c +37 -28
@@ -3406,10 +3406,43 @@ static bool ext4_inode_datasync_dirty(struct inode *inode)return inode->i_state &I_DIRTY_DATASYNC ; } +static int ext4_set_iomap (struct inode *inode,struct iomap *iomap,u16 type, +unsigned long first_block,struct ext4_map_blocks *map) +{ +u8 blkbits = inode->i_blkbits; + + iomap->flags =0 ; +if (ext4_inode_datasync_dirty (inode)) + iomap->flags |=IOMAP_F_DIRTY ; + iomap->bdev = inode->i_sb->s_bdev; + iomap->dax_dev =EXT4_SB (inode->i_sb)->s_daxdev; + iomap->offset = (u64 ) first_block << blkbits; + iomap->length = (u64 ) map->m_len << blkbits; + +if (type) { + iomap->type = type; + iomap->addr =IOMAP_NULL_ADDR ; + }else { +if (map->m_flags &EXT4_MAP_MAPPED ) { + iomap->type =IOMAP_MAPPED ; + }else if (map->m_flags &EXT4_MAP_UNWRITTEN ) { + iomap->type =IOMAP_UNWRITTEN ; + }else { +WARN_ON_ONCE (1 ); +return -EIO ; + } + iomap->addr = (u64 ) map->m_pblk << blkbits; + } + +if (map->m_flags &EXT4_MAP_NEW ) + iomap->flags |=IOMAP_F_NEW ; +return 0 ; +} +static int ext4_iomap_begin (struct inode *inode,loff_t offset,loff_t length,unsigned flags,struct iomap *iomap) { -struct ext4_sb_info *sbi =EXT4_SB (inode->i_sb); +u16 type =0 ;unsigned int blkbits = inode->i_blkbits;unsigned long first_block, last_block;struct ext4_map_blocks map;
@@ -3523,33 +3556,9 @@ static int ext4_iomap_begin(struct inode *inode, loff_t offset, loff_t length,return ret; } - iomap->flags =0 ; -if (ext4_inode_datasync_dirty (inode)) - iomap->flags |=IOMAP_F_DIRTY ; - iomap->bdev = inode->i_sb->s_bdev; - iomap->dax_dev = sbi->s_daxdev; - iomap->offset = (u64 )first_block << blkbits; - iomap->length = (u64 )map.m_len << blkbits; - -if (ret ==0 ) { - iomap->type = delalloc ?IOMAP_DELALLOC :IOMAP_HOLE ; - iomap->addr =IOMAP_NULL_ADDR ; - }else { -if (map.m_flags &EXT4_MAP_MAPPED ) { - iomap->type =IOMAP_MAPPED ; - }else if (map.m_flags &EXT4_MAP_UNWRITTEN ) { - iomap->type =IOMAP_UNWRITTEN ; - }else { -WARN_ON_ONCE (1 ); -return -EIO ; - } - iomap->addr = (u64 )map.m_pblk << blkbits; - } - -if (map.m_flags &EXT4_MAP_NEW ) - iomap->flags |=IOMAP_F_NEW ; - -return 0 ; +if (!ret) + type = delalloc ?IOMAP_DELALLOC :IOMAP_HOLE ; +return ext4_set_iomap (inode, iomap, type, first_block, &map); } static int ext4_iomap_end(struct inode *inode, loff_t offset, loff_t length,
Signature · 1 line
2.20.1
Jan Kara
reviewerRe: [PATCH v4 1/8] ext4: move out iomap field population into separate helper
Quoted 35 lines · Matthew Bobrowski
Separate the iomap field population chunk into a separate simple helper routine. This helps reducing the overall clutter within the
ext4_iomap_begin()callback, especially as we move across more code to make use of iomap infrastructure.Signed-off-by Matthew Bobrowski <[email protected]>--- fs/ext4/inode.c | 65 ++++++++++++++++++++++++++++--------------------- 1 file changed, 37 insertions(+), 28 deletions(-)fs/ext4/inode.c +17
-0@@ -3406,10 +3406,43 @@ static bool ext4_inode_datasync_dirty(struct inode *inode)return inode->i_state &I_DIRTY_DATASYNC ; } +static int ext4_set_iomap (struct inode *inode,struct iomap *iomap,u16 type, +unsigned long first_block,struct ext4_map_blocks *map) +{ +u8 blkbits = inode->i_blkbits; + + iomap->flags =0 ; +if (ext4_inode_datasync_dirty (inode)) + iomap->flags |=IOMAP_F_DIRTY ; + iomap->bdev = inode->i_sb->s_bdev; + iomap->dax_dev =EXT4_SB (inode->i_sb)->s_daxdev; + iomap->offset = (u64 ) first_block << blkbits; + iomap->length = (u64 ) map->m_len << blkbits; + +if (type) { + iomap->type = type; + iomap->addr =IOMAP_NULL_ADDR ; + }else {
fs/ext4/inode.c static bool ext4_inode_datasync_dirty(struct inode *inode) · line 3435
Quoted 10 lines
fs/ext4/inode.c +10
-0+if (map->m_flags &EXT4_MAP_MAPPED ) { + iomap->type =IOMAP_MAPPED ; + }else if (map->m_flags &EXT4_MAP_UNWRITTEN ) { + iomap->type =IOMAP_UNWRITTEN ; + }else { +WARN_ON_ONCE (1 ); +return -EIO ; + } + iomap->addr = (u64 ) map->m_pblk << blkbits; + }
Looking at this function now, the 'type' argument looks a bit weird. Can we perhaps just remove the 'type' argument and change the above to:
if (map->m_flags & (EXT4_MAP_MAPPED | EXT4_MAP_UNWRITTEN)) {
if (map->m_flags & EXT4_MAP_MAPPED)
iomap->type = IOMAP_MAPPED;
else if (map->m_flags & EXT4_MAP_UNWRITTEN)
iomap->type = IOMAP_UNWRITTEN;
iomap->addr = (u64) map->m_pblk << blkbits;
} else {
iomap->type = IOMAP_HOLE;
iomap->addr = IOMAP_NULL_ADDR;
}And then in ext4_iomap_begin() we overwrite the type to:
if (delalloc && iomap->type == IOMAP_HOLE) iomap->type = IOMAP_DELALLOC;
That would IMO make ext4_set_iomap() arguments harder to get wrong.
Honza
Quoted 54 lines
fs/ext4/inode.c +10
-28+ +if (map->m_flags &EXT4_MAP_NEW ) + iomap->flags |=IOMAP_F_NEW ; +return 0 ; +} +static int ext4_iomap_begin (struct inode *inode,loff_t offset,loff_t length,unsigned flags,struct iomap *iomap) { -struct ext4_sb_info *sbi =EXT4_SB (inode->i_sb); +u16 type =0 ;unsigned int blkbits = inode->i_blkbits;unsigned long first_block, last_block;struct ext4_map_blocks map;@@ -3523,33 +3556,9 @@ static int ext4_iomap_begin(struct inode *inode, loff_t offset, loff_t length,return ret; } - iomap->flags =0 ; -if (ext4_inode_datasync_dirty (inode)) - iomap->flags |=IOMAP_F_DIRTY ; - iomap->bdev = inode->i_sb->s_bdev; - iomap->dax_dev = sbi->s_daxdev; - iomap->offset = (u64 )first_block << blkbits; - iomap->length = (u64 )map.m_len << blkbits; - -if (ret ==0 ) { - iomap->type = delalloc ?IOMAP_DELALLOC :IOMAP_HOLE ; - iomap->addr =IOMAP_NULL_ADDR ; - }else { -if (map.m_flags &EXT4_MAP_MAPPED ) { - iomap->type =IOMAP_MAPPED ; - }else if (map.m_flags &EXT4_MAP_UNWRITTEN ) { - iomap->type =IOMAP_UNWRITTEN ; - }else { -WARN_ON_ONCE (1 ); -return -EIO ; - } - iomap->addr = (u64 )map.m_pblk << blkbits; - } - -if (map.m_flags &EXT4_MAP_NEW ) - iomap->flags |=IOMAP_F_NEW ; - -return 0 ; +if (!ret) + type = delalloc ?IOMAP_DELALLOC :IOMAP_HOLE ; +return ext4_set_iomap (inode, iomap, type, first_block, &map); } static int ext4_iomap_end(struct inode *inode, loff_t offset, loff_t length,Signature · 1 line
2.20.1
Signature · 2 lines
Jan Kara <[email protected]> SUSE Labs, CR
Re: [PATCH v4 1/8] ext4: move out iomap field population into separate helper
Quoted 23 lines · Jan Kara
Quoted 22 lines · Matthew Bobrowski
fs/ext4/inode.c +22
-0+static int ext4_set_iomap (struct inode *inode,struct iomap *iomap,u16 type, +unsigned long first_block,struct ext4_map_blocks *map) +{ +u8 blkbits = inode->i_blkbits; + + iomap->flags =0 ; +if (ext4_inode_datasync_dirty (inode)) + iomap->flags |=IOMAP_F_DIRTY ; + iomap->bdev = inode->i_sb->s_bdev; + iomap->dax_dev =EXT4_SB (inode->i_sb)->s_daxdev; + iomap->offset = (u64 ) first_block << blkbits; + iomap->length = (u64 ) map->m_len << blkbits; + +if (type) { + iomap->type = type; + iomap->addr =IOMAP_NULL_ADDR ; + }else { +if (map->m_flags &EXT4_MAP_MAPPED ) { + iomap->type =IOMAP_MAPPED ; + }else if (map->m_flags &EXT4_MAP_UNWRITTEN ) { + iomap->type =IOMAP_UNWRITTEN ; + }else {
Quoted 8 lines
fs/ext4/inode.c static bool ext4_inode_datasync_dirty(struct inode *inode) · line 3435
Quoted 5 lines
fs/ext4/inode.c +5
-0+WARN_ON_ONCE (1 ); +return -EIO ; + } + iomap->addr = (u64 ) map->m_pblk << blkbits; + }Looking at this function now, the 'type' argument looks a bit weird. Can we perhaps just remove the 'type' argument and change the above to:
We can, but refer to the point below.
Quoted 11 lines
if (map->m_flags & (EXT4_MAP_MAPPED | EXT4_MAP_UNWRITTEN)) {
if (map->m_flags & EXT4_MAP_MAPPED)
iomap->type = IOMAP_MAPPED;
else if (map->m_flags & EXT4_MAP_UNWRITTEN)
iomap->type = IOMAP_UNWRITTEN;
iomap->addr = (u64) map->m_pblk << blkbits;
} else {
iomap->type = IOMAP_HOLE;
iomap->addr = IOMAP_NULL_ADDR;
}Quoted 6 lines
And then in
ext4_iomap_begin()we overwrite the type to:if (delalloc && iomap->type == IOMAP_HOLE) iomap->type = IOMAP_DELALLOC;That would IMO make
ext4_set_iomap()arguments harder to get wrong.
I was thinking about this while doing a bunch of other things at work today. I'm kind of aligned with what Christoph mentioned around possibly duplicating some of the post 'iomap->type' setting from both current and any future ext4_set_iomap() callers. In addition to this, my thought was that if we're populating the iomap structure with values respectively, then it would make most sense to encapsulate those routines, if possible, within the ext4_set_iomap() as that's the sole purpose of the function.
However, no real strong objections for dropping 'type', but I just wanted to share my thoughts.
Also, yes, we probably can drop 'first_block' from the list of arguments here as we can derive that from 'map' and set 'iomap->type' accordingly...
--<M>--
Jan Kara
reviewerRe: [PATCH v4 1/8] ext4: move out iomap field population into separate helper
Quoted 53 lines · Matthew Bobrowski
Quoted 23 lines · Jan Kara
Quoted 22 lines · Matthew Bobrowski
fs/ext4/inode.c +22
-0+static int ext4_set_iomap (struct inode *inode,struct iomap *iomap,u16 type, +unsigned long first_block,struct ext4_map_blocks *map) +{ +u8 blkbits = inode->i_blkbits; + + iomap->flags =0 ; +if (ext4_inode_datasync_dirty (inode)) + iomap->flags |=IOMAP_F_DIRTY ; + iomap->bdev = inode->i_sb->s_bdev; + iomap->dax_dev =EXT4_SB (inode->i_sb)->s_daxdev; + iomap->offset = (u64 ) first_block << blkbits; + iomap->length = (u64 ) map->m_len << blkbits; + +if (type) { + iomap->type = type; + iomap->addr =IOMAP_NULL_ADDR ; + }else { +if (map->m_flags &EXT4_MAP_MAPPED ) { + iomap->type =IOMAP_MAPPED ; + }else if (map->m_flags &EXT4_MAP_UNWRITTEN ) { + iomap->type =IOMAP_UNWRITTEN ; + }else {Quoted 8 lines
fs/ext4/inode.c static bool ext4_inode_datasync_dirty(struct inode *inode) · line 3435
Quoted 5 lines
fs/ext4/inode.c +5
-0+WARN_ON_ONCE (1 ); +return -EIO ; + } + iomap->addr = (u64 ) map->m_pblk << blkbits; + }Looking at this function now, the 'type' argument looks a bit weird. Can we perhaps just remove the 'type' argument and change the above to:
We can, but refer to the point below.
Quoted 11 lines
if (map->m_flags & (EXT4_MAP_MAPPED | EXT4_MAP_UNWRITTEN)) { if (map->m_flags & EXT4_MAP_MAPPED) iomap->type = IOMAP_MAPPED; else if (map->m_flags & EXT4_MAP_UNWRITTEN) iomap->type = IOMAP_UNWRITTEN; iomap->addr = (u64) map->m_pblk << blkbits; } else { iomap->type = IOMAP_HOLE; iomap->addr = IOMAP_NULL_ADDR; }Quoted 6 lines
And then in
ext4_iomap_begin()we overwrite the type to:if (delalloc && iomap->type == IOMAP_HOLE) iomap->type = IOMAP_DELALLOC;That would IMO make
ext4_set_iomap()arguments harder to get wrong.
Quoted 8 lines
I was thinking about this while doing a bunch of other things at work today. I'm kind of aligned with what Christoph mentioned around possibly duplicating some of the post '
iomap->type' setting from both current and any futureext4_set_iomap()callers. In addition to this, my thought was that if we're populating the iomap structure with values respectively, then it would make most sense to encapsulate those routines, if possible, within theext4_set_iomap()as that's the sole purpose of the function.
Well, what I dislike about 'type' argument is the inconsistency in it's handling. It is useful only for HOLE/DELALLOC, anything else will just give you invalid iomap and you have to be careful to pass 0 in that case.
I understand the concern about possible duplication but since only IOMAP_REPORT cares about IOMAP_DELALLOC, I'm not much concerned about it. But another sensible API would be to optionally pass 'struct extent_status *es' argument to ext4_set_iomap() and if this argument is non-NULL, ext4_set_iomap() will handle the intersection of ext4_map_blocks and extent_status and deduce appropriate resulting type from that.
Honza
Signature · 2 lines
Jan Kara <[email protected]> SUSE Labs, CR
Re: [PATCH v4 1/8] ext4: move out iomap field population into separate helper
Quoted 67 lines · Jan Kara
Quoted 53 lines · Matthew Bobrowski
Quoted 23 lines · Jan Kara
Quoted 22 lines · Matthew Bobrowski
fs/ext4/inode.c +22
-0+static int ext4_set_iomap (struct inode *inode,struct iomap *iomap,u16 type, +unsigned long first_block,struct ext4_map_blocks *map) +{ +u8 blkbits = inode->i_blkbits; + + iomap->flags =0 ; +if (ext4_inode_datasync_dirty (inode)) + iomap->flags |=IOMAP_F_DIRTY ; + iomap->bdev = inode->i_sb->s_bdev; + iomap->dax_dev =EXT4_SB (inode->i_sb)->s_daxdev; + iomap->offset = (u64 ) first_block << blkbits; + iomap->length = (u64 ) map->m_len << blkbits; + +if (type) { + iomap->type = type; + iomap->addr =IOMAP_NULL_ADDR ; + }else { +if (map->m_flags &EXT4_MAP_MAPPED ) { + iomap->type =IOMAP_MAPPED ; + }else if (map->m_flags &EXT4_MAP_UNWRITTEN ) { + iomap->type =IOMAP_UNWRITTEN ; + }else {Quoted 8 lines
fs/ext4/inode.c static bool ext4_inode_datasync_dirty(struct inode *inode) · line 3435
Quoted 5 lines
fs/ext4/inode.c +5
-0+WARN_ON_ONCE (1 ); +return -EIO ; + } + iomap->addr = (u64 ) map->m_pblk << blkbits; + }Looking at this function now, the 'type' argument looks a bit weird. Can we perhaps just remove the 'type' argument and change the above to:
We can, but refer to the point below.
Quoted 11 lines
if (map->m_flags & (EXT4_MAP_MAPPED | EXT4_MAP_UNWRITTEN)) { if (map->m_flags & EXT4_MAP_MAPPED) iomap->type = IOMAP_MAPPED; else if (map->m_flags & EXT4_MAP_UNWRITTEN) iomap->type = IOMAP_UNWRITTEN; iomap->addr = (u64) map->m_pblk << blkbits; } else { iomap->type = IOMAP_HOLE; iomap->addr = IOMAP_NULL_ADDR; }Quoted 6 lines
And then in
ext4_iomap_begin()we overwrite the type to:if (delalloc && iomap->type == IOMAP_HOLE) iomap->type = IOMAP_DELALLOC;That would IMO make
ext4_set_iomap()arguments harder to get wrong.Quoted 8 lines
I was thinking about this while doing a bunch of other things at work today. I'm kind of aligned with what Christoph mentioned around possibly duplicating some of the post '
iomap->type' setting from both current and any futureext4_set_iomap()callers. In addition to this, my thought was that if we're populating the iomap structure with values respectively, then it would make most sense to encapsulate those routines, if possible, within theext4_set_iomap()as that's the sole purpose of the function.Well, what I dislike about 'type' argument is the inconsistency in it's handling. It is useful only for HOLE/DELALLOC, anything else will just give you invalid iomap and you have to be careful to pass 0 in that case.
Quoted 6 lines
I understand the concern about possible duplication but since only
IOMAP_REPORTcares aboutIOMAP_DELALLOC, I'm not much concerned about it. But another sensible API would be to optionally pass 'structextent_status*es' argument toext4_set_iomap()and if this argument is non-NULL,ext4_set_iomap()will handle the intersection ofext4_map_blocksandextent_statusand deduce appropriate resulting type from that.
I see and thank you for sharing your view point. Let's go with what you originally proposed, which is dropping the 'type' argument and then handling IOMAP_DELALLOC within ext4_set_iomap(). No real hard objections. :)
--<M>--
Re: [PATCH v4 1/8] ext4: move out iomap field population into separate helper
In reply to Matthew BobrowskiSome minor comments apart from Jan comments.
Quoted 15 lines · Matthew Bobrowski
Separate the iomap field population chunk into a separate simple helper routine. This helps reducing the overall clutter within the
ext4_iomap_begin()callback, especially as we move across more code to make use of iomap infrastructure.Signed-off-by Matthew Bobrowski <[email protected]>--- fs/ext4/inode.c | 65 ++++++++++++++++++++++++++++--------------------- 1 file changed, 37 insertions(+), 28 deletions(-)fs/ext4/inode.c +0
-0
fs/ext4/inode.c static bool ext4_inode_datasync_dirty(struct inode *inode) · line 3410
Quoted 5 lines
fs/ext4/inode.c +2
-0@@ -3406,10 +3406,43 @@ static bool ext4_inode_datasync_dirty(struct inode *inode)return inode->i_state &I_DIRTY_DATASYNC ; } +static int ext4_set_iomap (struct inode *inode,struct iomap *iomap,u16 type, +unsigned long first_block,struct ext4_map_blocks *map)
Line beyond 80 chars. Please check with checkpatch once.
We can also get rid of "first_block" argument here. Also the "type" argument also looks confusing. Please see comment on patch 3.
Quoted 77 lines
fs/ext4/inode.c +35
-28+{ +u8 blkbits = inode->i_blkbits; + + iomap->flags =0 ; +if (ext4_inode_datasync_dirty (inode)) + iomap->flags |=IOMAP_F_DIRTY ; + iomap->bdev = inode->i_sb->s_bdev; + iomap->dax_dev =EXT4_SB (inode->i_sb)->s_daxdev; + iomap->offset = (u64 ) first_block << blkbits; + iomap->length = (u64 ) map->m_len << blkbits; + +if (type) { + iomap->type = type; + iomap->addr =IOMAP_NULL_ADDR ; + }else { +if (map->m_flags &EXT4_MAP_MAPPED ) { + iomap->type =IOMAP_MAPPED ; + }else if (map->m_flags &EXT4_MAP_UNWRITTEN ) { + iomap->type =IOMAP_UNWRITTEN ; + }else { +WARN_ON_ONCE (1 ); +return -EIO ; + } + iomap->addr = (u64 ) map->m_pblk << blkbits; + } + +if (map->m_flags &EXT4_MAP_NEW ) + iomap->flags |=IOMAP_F_NEW ; +return 0 ; +} +static int ext4_iomap_begin (struct inode *inode,loff_t offset,loff_t length,unsigned flags,struct iomap *iomap) { -struct ext4_sb_info *sbi =EXT4_SB (inode->i_sb); +u16 type =0 ;unsigned int blkbits = inode->i_blkbits;unsigned long first_block, last_block;struct ext4_map_blocks map;@@ -3523,33 +3556,9 @@ static int ext4_iomap_begin(struct inode *inode, loff_t offset, loff_t length,return ret; } - iomap->flags =0 ; -if (ext4_inode_datasync_dirty (inode)) - iomap->flags |=IOMAP_F_DIRTY ; - iomap->bdev = inode->i_sb->s_bdev; - iomap->dax_dev = sbi->s_daxdev; - iomap->offset = (u64 )first_block << blkbits; - iomap->length = (u64 )map.m_len << blkbits; - -if (ret ==0 ) { - iomap->type = delalloc ?IOMAP_DELALLOC :IOMAP_HOLE ; - iomap->addr =IOMAP_NULL_ADDR ; - }else { -if (map.m_flags &EXT4_MAP_MAPPED ) { - iomap->type =IOMAP_MAPPED ; - }else if (map.m_flags &EXT4_MAP_UNWRITTEN ) { - iomap->type =IOMAP_UNWRITTEN ; - }else { -WARN_ON_ONCE (1 ); -return -EIO ; - } - iomap->addr = (u64 )map.m_pblk << blkbits; - } - -if (map.m_flags &EXT4_MAP_NEW ) - iomap->flags |=IOMAP_F_NEW ; - -return 0 ; +if (!ret) + type = delalloc ?IOMAP_DELALLOC :IOMAP_HOLE ; +return ext4_set_iomap (inode, iomap, type, first_block, &map); } static int ext4_iomap_end(struct inode *inode, loff_t offset, loff_t length,
Re: [PATCH v4 1/8] ext4: move out iomap field population into separate helper
Quoted 1 line · Ritesh Harjani
We can also get rid of "
first_block" argument here.
That would just duplicate filling it out in all callers, so why?
Re: [PATCH v4 1/8] ext4: move out iomap field population into separate helper
Quoted 5 lines · Christoph Hellwig
Quoted 1 line · Ritesh Harjani
We can also get rid of "
first_block" argument here.That would just duplicate filling it out in all callers, so why?
What I meant is "first_block" is same as map->m_lblk. (unless ext4_map_blocks can change map->m_lblk, which AFAICT, it should not).
So why pass an extra argument when we are already passing 'map' structure.
So we can fill iomap->offset using map->m_lblk in ext4_set_iomap() function.
-ritesh
Re: [PATCH v4 1/8] ext4: move out iomap field population into separate helper
Quoted 7 lines · Ritesh Harjani
Quoted 5 lines · Christoph Hellwig
Quoted 1 line · Ritesh Harjani
We can also get rid of "
first_block" argument here.That would just duplicate filling it out in all callers, so why?
Quoted 7 lines
What I meant is "
first_block" is same asmap->m_lblk. (unlessext4_map_blockscan changemap->m_lblk, which AFAICT, it should not).
So why pass an extra argument when we are already passing 'map' structure.
So we can filliomap->offsetusingmap->m_lblkinext4_set_iomap()function.
What you're saying makes sense Ritesh and I will update it as such. I believe what Christoph was actually referring to was what I explained to Jan to the email that I just sent out. This was around the possible code duplication and having some iomap value setting related logic outside ext4_set_iomap(), when in fact there's no real reason why it can't be inside.
--<M>--
PATCH v4 2/8 ext4: move out IOMAP_WRITE path into separate helper
In reply to Matthew BobrowskiIn preparation for porting across the direct I/O path to iomap, split out the IOMAP_WRITE logic into a separate helper. This way, we don't need to clutter the ext4_iomap_begin() callback.
--- fs/ext4/inode.c | 110 ++++++++++++++++++++++++++---------------------- 1 file changed, 60 insertions(+), 50 deletions(-)
fs/ext4/inode.c +60 -50
@@ -3439,6 +3439,62 @@ static int ext4_set_iomap(struct inode *inode, struct iomap *iomap, u16 type,return 0 ; } +static int ext4_iomap_alloc (struct inode *inode, +unsigned flags, +unsigned long first_block, +struct ext4_map_blocks *map) +{ +handle_t *handle; +u8 blkbits = inode->i_blkbits; +int ret, dio_credits, retries =0 ; + +/* +* Trim mapping request to the maximum value that we can map +* at once for direct I/O. +*/ +if (map->m_len >DIO_MAX_BLOCKS ) + map->m_len =DIO_MAX_BLOCKS ; + dio_credits =ext4_chunk_trans_blocks (inode, map->m_len); +retry: +/* +* Either we allocate blocks and then we don't get unwritten +* extent so we have reserved enough credits, or the blocks +* are already allocated and unwritten. In that case, the +* extent conversion fits in the credits as well. +*/ + handle =ext4_journal_start (inode,EXT4_HT_MAP_BLOCKS , dio_credits); +if (IS_ERR (handle)) +return PTR_ERR (handle); + + ret =ext4_map_blocks (handle, inode, map,EXT4_GET_BLOCKS_CREATE_ZERO ); +if (ret <0 ) + goto journal_stop; + +/* +* If we have allocated blocks beyond the EOF, we need to make +* sure that they get truncate if we crash before updating the +* inode size metadata in ext4_iomap_end(). For faults, we +* don't need to do that (and cannot due to the orphan list +* operations needing an inode_lock()). If we happen to +* instantiate blocks beyond EOF, it is because we race with a +* truncate operation, which already has added the inode onto +* the orphan list. +*/ +if (!(flags &IOMAP_FAULT ) && first_block + map->m_len > + (i_size_read (inode) + (1 << blkbits) -1 ) >> blkbits) { +int err; + + err =ext4_orphan_add (handle, inode); +if (err <0 ) + ret = err; + } +journal_stop: +ext4_journal_stop (handle); +if (ret == -ENOSPC &&ext4_should_retry_alloc (inode->i_sb, &retries)) + goto retry; +return ret; +} +static int ext4_iomap_begin (struct inode *inode,loff_t offset,loff_t length,unsigned flags,struct iomap *iomap) {
@@ -3500,62 +3556,16 @@ static int ext4_iomap_begin(struct inode *inode, loff_t offset, loff_t length, } } }else if (flags &IOMAP_WRITE ) { -int dio_credits; -handle_t *handle; -int retries =0 ; - -/* Trim mapping request to maximum we can map at once for DIO */ -if (map.m_len >DIO_MAX_BLOCKS ) - map.m_len =DIO_MAX_BLOCKS ; - dio_credits =ext4_chunk_trans_blocks (inode, map.m_len); -retry: -/* -* Either we allocate blocks and then we don't get unwritten -* extent so we have reserved enough credits, or the blocks -* are already allocated and unwritten and in that case -* extent conversion fits in the credits as well. -*/ - handle =ext4_journal_start (inode,EXT4_HT_MAP_BLOCKS , - dio_credits); -if (IS_ERR (handle)) -return PTR_ERR (handle); - - ret =ext4_map_blocks (handle, inode, &map, -EXT4_GET_BLOCKS_CREATE_ZERO ); -if (ret <0 ) { -ext4_journal_stop (handle); -if (ret == -ENOSPC && -ext4_should_retry_alloc (inode->i_sb, &retries)) - goto retry; -return ret; - } - -/* -* If we added blocks beyond i_size, we need to make sure they -* will get truncated if we crash before updating i_size in -* ext4_iomap_end(). For faults we don't need to do that (and -* even cannot because for orphan list operations inode_lock is -* required) - if we happen to instantiate block beyond i_size, -* it is because we race with truncate which has already added -* the inode to the orphan list. -*/ -if (!(flags &IOMAP_FAULT ) && first_block + map.m_len > - (i_size_read (inode) + (1 << blkbits) -1 ) >> blkbits) { -int err; - - err =ext4_orphan_add (handle, inode); -if (err <0 ) { -ext4_journal_stop (handle); -return err; - } - } -ext4_journal_stop (handle); + ret =ext4_iomap_alloc (inode, flags, first_block, &map); }else { ret =ext4_map_blocks (NULL , inode, &map,0 );if (ret <0 )return ret; } +if (ret <0 ) +return ret; +if (!ret) type = delalloc ?IOMAP_DELALLOC :IOMAP_HOLE ;return ext4_set_iomap (inode, iomap, type, first_block, &map);
Signature · 1 line
2.20.1
Re: [PATCH v4 2/8] ext4: move out IOMAP_WRITE path into separate helper
Quoted 5 lines · Matthew Bobrowski
In preparation for porting across the direct I/O path to iomap, split out the
IOMAP_WRITElogic into a separate helper. This way, we don't need to clutter theext4_iomap_begin()callback.Signed-off-by Matthew Bobrowski <[email protected]>
The patch looks good to me. You can add:
Just please reformat the comments to use full 80 column lines. Your Emacs still doesn't seem to get it :)
Honza
Quoted 141 lines
--- fs/ext4/inode.c | 110 ++++++++++++++++++++++++++---------------------- 1 file changed, 60 insertions(+), 50 deletions(-)fs/ext4/inode.c +60
-50@@ -3439,6 +3439,62 @@ static int ext4_set_iomap(struct inode *inode, struct iomap *iomap, u16 type,return 0 ; } +static int ext4_iomap_alloc (struct inode *inode, +unsigned flags, +unsigned long first_block, +struct ext4_map_blocks *map) +{ +handle_t *handle; +u8 blkbits = inode->i_blkbits; +int ret, dio_credits, retries =0 ; + +/* +* Trim mapping request to the maximum value that we can map +* at once for direct I/O. +*/ +if (map->m_len >DIO_MAX_BLOCKS ) + map->m_len =DIO_MAX_BLOCKS ; + dio_credits =ext4_chunk_trans_blocks (inode, map->m_len); +retry: +/* +* Either we allocate blocks and then we don't get unwritten +* extent so we have reserved enough credits, or the blocks +* are already allocated and unwritten. In that case, the +* extent conversion fits in the credits as well. +*/ + handle =ext4_journal_start (inode,EXT4_HT_MAP_BLOCKS , dio_credits); +if (IS_ERR (handle)) +return PTR_ERR (handle); + + ret =ext4_map_blocks (handle, inode, map,EXT4_GET_BLOCKS_CREATE_ZERO ); +if (ret <0 ) + goto journal_stop; + +/* +* If we have allocated blocks beyond the EOF, we need to make +* sure that they get truncate if we crash before updating the +* inode size metadata in ext4_iomap_end(). For faults, we +* don't need to do that (and cannot due to the orphan list +* operations needing an inode_lock()). If we happen to +* instantiate blocks beyond EOF, it is because we race with a +* truncate operation, which already has added the inode onto +* the orphan list. +*/ +if (!(flags &IOMAP_FAULT ) && first_block + map->m_len > + (i_size_read (inode) + (1 << blkbits) -1 ) >> blkbits) { +int err; + + err =ext4_orphan_add (handle, inode); +if (err <0 ) + ret = err; + } +journal_stop: +ext4_journal_stop (handle); +if (ret == -ENOSPC &&ext4_should_retry_alloc (inode->i_sb, &retries)) + goto retry; +return ret; +} +static int ext4_iomap_begin (struct inode *inode,loff_t offset,loff_t length,unsigned flags,struct iomap *iomap) {@@ -3500,62 +3556,16 @@ static int ext4_iomap_begin(struct inode *inode, loff_t offset, loff_t length, } } }else if (flags &IOMAP_WRITE ) { -int dio_credits; -handle_t *handle; -int retries =0 ; - -/* Trim mapping request to maximum we can map at once for DIO */ -if (map.m_len >DIO_MAX_BLOCKS ) - map.m_len =DIO_MAX_BLOCKS ; - dio_credits =ext4_chunk_trans_blocks (inode, map.m_len); -retry: -/* -* Either we allocate blocks and then we don't get unwritten -* extent so we have reserved enough credits, or the blocks -* are already allocated and unwritten and in that case -* extent conversion fits in the credits as well. -*/ - handle =ext4_journal_start (inode,EXT4_HT_MAP_BLOCKS , - dio_credits); -if (IS_ERR (handle)) -return PTR_ERR (handle); - - ret =ext4_map_blocks (handle, inode, &map, -EXT4_GET_BLOCKS_CREATE_ZERO ); -if (ret <0 ) { -ext4_journal_stop (handle); -if (ret == -ENOSPC && -ext4_should_retry_alloc (inode->i_sb, &retries)) - goto retry; -return ret; - } - -/* -* If we added blocks beyond i_size, we need to make sure they -* will get truncated if we crash before updating i_size in -* ext4_iomap_end(). For faults we don't need to do that (and -* even cannot because for orphan list operations inode_lock is -* required) - if we happen to instantiate block beyond i_size, -* it is because we race with truncate which has already added -* the inode to the orphan list. -*/ -if (!(flags &IOMAP_FAULT ) && first_block + map.m_len > - (i_size_read (inode) + (1 << blkbits) -1 ) >> blkbits) { -int err; - - err =ext4_orphan_add (handle, inode); -if (err <0 ) { -ext4_journal_stop (handle); -return err; - } - } -ext4_journal_stop (handle); + ret =ext4_iomap_alloc (inode, flags, first_block, &map); }else { ret =ext4_map_blocks (NULL , inode, &map,0 );if (ret <0 )return ret; } +if (ret <0 ) +return ret; +if (!ret) type = delalloc ?IOMAP_DELALLOC :IOMAP_HOLE ;return ext4_set_iomap (inode, iomap, type, first_block, &map);Signature · 1 line
2.20.1
Signature · 2 lines
Jan Kara <[email protected]> SUSE Labs, CR
Re: [PATCH v4 2/8] ext4: move out IOMAP_WRITE path into separate helper
Quoted 5 lines · Jan Kara
Quoted 4 lines · Matthew Bobrowski
In preparation for porting across the direct I/O path to iomap, split out the
IOMAP_WRITElogic into a separate helper. This way, we don't need to clutter theext4_iomap_begin()callback.
Quoted 8 lines
Quoted 1 line
Signed-off-by Matthew Bobrowski <[email protected]>The patch looks good to me. You can add:
Reviewed-by Jan Kara <[email protected]>Just please reformat the comments to use full 80 column lines. Your Emacs still doesn't seem to get it :)
*nod* :)
--<M>--
Re: [PATCH v4 2/8] ext4: move out IOMAP_WRITE path into separate helper
In reply to Matthew BobrowskiQuoted 5 lines · Matthew Bobrowski
In preparation for porting across the direct I/O path to iomap, split out the
IOMAP_WRITElogic into a separate helper. This way, we don't need to clutter theext4_iomap_begin()callback.Signed-off-by Matthew Bobrowski <[email protected]>
Minor comment, but otherwise.
Patch looks good to me. You may add:
Quoted 116 lines
--- fs/ext4/inode.c | 110 ++++++++++++++++++++++++++---------------------- 1 file changed, 60 insertions(+), 50 deletions(-)fs/ext4/inode.c +56
-41@@ -3439,6 +3439,62 @@ static int ext4_set_iomap(struct inode *inode, struct iomap *iomap, u16 type,return 0 ; } +static int ext4_iomap_alloc (struct inode *inode, +unsigned flags, +unsigned long first_block, +struct ext4_map_blocks *map) +{ +handle_t *handle; +u8 blkbits = inode->i_blkbits; +int ret, dio_credits, retries =0 ; + +/* +* Trim mapping request to the maximum value that we can map +* at once for direct I/O. +*/ +if (map->m_len >DIO_MAX_BLOCKS ) + map->m_len =DIO_MAX_BLOCKS ; + dio_credits =ext4_chunk_trans_blocks (inode, map->m_len); +retry: +/* +* Either we allocate blocks and then we don't get unwritten +* extent so we have reserved enough credits, or the blocks +* are already allocated and unwritten. In that case, the +* extent conversion fits in the credits as well. +*/ + handle =ext4_journal_start (inode,EXT4_HT_MAP_BLOCKS , dio_credits); +if (IS_ERR (handle)) +return PTR_ERR (handle); + + ret =ext4_map_blocks (handle, inode, map,EXT4_GET_BLOCKS_CREATE_ZERO ); +if (ret <0 ) + goto journal_stop; + +/* +* If we have allocated blocks beyond the EOF, we need to make +* sure that they get truncate if we crash before updating the +* inode size metadata in ext4_iomap_end(). For faults, we +* don't need to do that (and cannot due to the orphan list +* operations needing an inode_lock()). If we happen to +* instantiate blocks beyond EOF, it is because we race with a +* truncate operation, which already has added the inode onto +* the orphan list. +*/ +if (!(flags &IOMAP_FAULT ) && first_block + map->m_len > + (i_size_read (inode) + (1 << blkbits) -1 ) >> blkbits) { +int err; + + err =ext4_orphan_add (handle, inode); +if (err <0 ) + ret = err; + } +journal_stop: +ext4_journal_stop (handle); +if (ret == -ENOSPC &&ext4_should_retry_alloc (inode->i_sb, &retries)) + goto retry; +return ret; +} +static int ext4_iomap_begin (struct inode *inode,loff_t offset,loff_t length,unsigned flags,struct iomap *iomap) {@@ -3500,62 +3556,16 @@ static int ext4_iomap_begin(struct inode *inode, loff_t offset, loff_t length, } } }else if (flags &IOMAP_WRITE ) { -int dio_credits; -handle_t *handle; -int retries =0 ; - -/* Trim mapping request to maximum we can map at once for DIO */ -if (map.m_len >DIO_MAX_BLOCKS ) - map.m_len =DIO_MAX_BLOCKS ; - dio_credits =ext4_chunk_trans_blocks (inode, map.m_len); -retry: -/* -* Either we allocate blocks and then we don't get unwritten -* extent so we have reserved enough credits, or the blocks -* are already allocated and unwritten and in that case -* extent conversion fits in the credits as well. -*/ - handle =ext4_journal_start (inode,EXT4_HT_MAP_BLOCKS , - dio_credits); -if (IS_ERR (handle)) -return PTR_ERR (handle); - - ret =ext4_map_blocks (handle, inode, &map, -EXT4_GET_BLOCKS_CREATE_ZERO ); -if (ret <0 ) { -ext4_journal_stop (handle); -if (ret == -ENOSPC && -ext4_should_retry_alloc (inode->i_sb, &retries)) - goto retry; -return ret; - } - -/* -* If we added blocks beyond i_size, we need to make sure they -* will get truncated if we crash before updating i_size in -* ext4_iomap_end(). For faults we don't need to do that (and -* even cannot because for orphan list operations inode_lock is -* required) - if we happen to instantiate block beyond i_size, -* it is because we race with truncate which has already added -* the inode to the orphan list. -*/ -if (!(flags &IOMAP_FAULT ) && first_block + map.m_len > - (i_size_read (inode) + (1 << blkbits) -1 ) >> blkbits) {
fs/ext4/inode.c static int ext4_iomap_begin(struct inode *inode, loff_t offset, loff_t length, · line 3559
Quoted 10 lines
fs/ext4/inode.c +1
-9-int err; - - err =ext4_orphan_add (handle, inode); -if (err <0 ) { -ext4_journal_stop (handle); -return err; - } - } -ext4_journal_stop (handle); + ret =ext4_iomap_alloc (inode, flags, first_block, &map);
We don't need "first_block" argument here. Since map->m_lblk saves first_block directly above in the same function.
No strong objection against ext4_iomap_alloc, but maybe ext4_iomap_map_write sounds better? Either way is fine though.
Quoted 13 lines
fs/ext4/inode.c +3
-0}else { ret =ext4_map_blocks (NULL , inode, &map,0 );if (ret <0 )return ret; } +if (ret <0 ) +return ret; +if (!ret) type = delalloc ?IOMAP_DELALLOC :IOMAP_HOLE ;return ext4_set_iomap (inode, iomap, type, first_block, &map);
Re: [PATCH v4 2/8] ext4: move out IOMAP_WRITE path into separate helper
Quoted 5 lines · Ritesh Harjani
On 10/3/19 5:03 PM, Matthew Bobrowski wrote:
Minor comment, but otherwise.
Patch looks good to me. You may add:Reviewed-by Ritesh Harjani <[email protected]>
*nod* - Thank you!
Quoted 53 lines
Quoted 53 lines
static int ext4_iomap_begin(struct inode *inode,
loff_toffset,loff_tlength,
unsigned flags, struct iomap *iomap)
{fs/ext4/inode.c +0
-46@@ -3500,62 +3556,16 @@ static int ext4_iomap_begin(struct inode *inode, loff_t offset, loff_t length, } } }else if (flags &IOMAP_WRITE ) { -int dio_credits; -handle_t *handle; -int retries =0 ; - -/* Trim mapping request to maximum we can map at once for DIO */ -if (map.m_len >DIO_MAX_BLOCKS ) - map.m_len =DIO_MAX_BLOCKS ; - dio_credits =ext4_chunk_trans_blocks (inode, map.m_len); -retry: -/* -* Either we allocate blocks and then we don't get unwritten -* extent so we have reserved enough credits, or the blocks -* are already allocated and unwritten and in that case -* extent conversion fits in the credits as well. -*/ - handle =ext4_journal_start (inode,EXT4_HT_MAP_BLOCKS , - dio_credits); -if (IS_ERR (handle)) -return PTR_ERR (handle); - - ret =ext4_map_blocks (handle, inode, &map, -EXT4_GET_BLOCKS_CREATE_ZERO ); -if (ret <0 ) { -ext4_journal_stop (handle); -if (ret == -ENOSPC && -ext4_should_retry_alloc (inode->i_sb, &retries)) - goto retry; -return ret; - } - -/* -* If we added blocks beyond i_size, we need to make sure they -* will get truncated if we crash before updating i_size in -* ext4_iomap_end(). For faults we don't need to do that (and -* even cannot because for orphan list operations inode_lock is -* required) - if we happen to instantiate block beyond i_size, -* it is because we race with truncate which has already added -* the inode to the orphan list. -*/ -if (!(flags &IOMAP_FAULT ) && first_block + map.m_len > - (i_size_read (inode) + (1 << blkbits) -1 ) >> blkbits) { -int err; - - err =ext4_orphan_add (handle, inode); -if (err <0 ) { -ext4_journal_stop (handle);
Quoted 8 lines
fs/ext4/inode.c static int ext4_iomap_begin(struct inode *inode, loff_t offset, loff_t length, · line 3559
Quoted 5 lines
fs/ext4/inode.c +1
-4-return err; - } - } -ext4_journal_stop (handle); + ret =ext4_iomap_alloc (inode, flags, first_block, &map);We don't need "
first_block" argument here. Sincemap->m_lblksavesfirst_blockdirectly above in the same function.
You're right. I will change that.
Quoted 3 lines
No strong objection against
ext4_iomap_alloc, but maybeext4_iomap_map_writesounds better? Either way is fine though.
I like 'ext4_iomap_alloc', because it's performing allocation in preparation for a write being performed on behalf of iomap. :)
--<M>--
PATCH v4 3/8 ext4: introduce new callback for IOMAP_REPORT operations
In reply to Matthew BobrowskiAs part of ext4_iomap_begin() cleanups and port across direct I/O path to make use of iomap infrastructure, we split IOMAP_REPORT operations into a separate ->iomap_begin() handler.
--- fs/ext4/ext4.h | 1 + fs/ext4/file.c | 6 ++- fs/ext4/inode.c | 129 ++++++++++++++++++++++++++++-------------------- 3 files changed, 80 insertions(+), 56 deletions(-)
fs/ext4/ext4.h +1 -0
@@ -3379,6 +3379,7 @@ static inline void ext4_clear_io_unwritten_flag(ext4_io_end_t *io_end) }extern const struct iomap_ops ext4_iomap_ops; +extern const struct iomap_ops ext4_iomap_report_ops;static inline int ext4_buffer_uptodate (struct buffer_head *bh) {
fs/ext4/file.c +4 -2
@@ -494,12 +494,14 @@ loff_t ext4_llseek(struct file *file, loff_t offset, int whence) maxbytes, i_size_read(inode));case SEEK_HOLE :inode_lock_shared (inode); - offset =iomap_seek_hole (inode, offset, &ext4_iomap_ops); + offset =iomap_seek_hole (inode, offset, + &ext4_iomap_report_ops);inode_unlock_shared (inode);break ;case SEEK_DATA :inode_lock_shared (inode); - offset =iomap_seek_data (inode, offset, &ext4_iomap_ops); + offset =iomap_seek_data (inode, offset, + &ext4_iomap_report_ops);inode_unlock_shared (inode);break ; }
fs/ext4/inode.c +75 -54
157 lines not on this page · raw message
Signature · 1 line
2.20.1
Re: [PATCH v4 3/8] ext4: introduce new callback for IOMAP_REPORT operations
Quoted 5 lines · Matthew Bobrowski
As part of
ext4_iomap_begin()cleanups and port across direct I/O path to make use of iomap infrastructure, we splitIOMAP_REPORToperations into a separate ->iomap_begin() handler.Signed-off-by Matthew Bobrowski <[email protected]>
The patch looks good to me. You can add:
It would just need small adjustments if you change patch 1 as I suggested:
Quoted 16 lines
fs/ext4/inode.c +16
-0+static u16 ext4_iomap_check_delalloc (struct inode *inode, +struct ext4_map_blocks *map) +{ +struct extent_status es; +ext4_lblk_t end = map->m_lblk + map->m_len -1 ; + +ext4_es_find_extent_range (inode, &ext4_es_is_delayed, map->m_lblk, + end, &es); + +/* Entire range is a hole */ +if (!es.es_len || es.es_lblk > end) +return IOMAP_HOLE ; +if (es.es_lblk <= map->m_lblk) { +ext4_lblk_t offset =0 ; + +if (es.es_lblk < map->m_lblk)
fs/ext4/inode.c static int ext4_set_iomap(struct inode *inode, struct iomap *iomap, u16 type, · line 3467
Quoted 10 lines
fs/ext4/inode.c +10
-0+ offset = map->m_lblk - es.es_lblk; + map->m_lblk = es.es_lblk + offset; + map->m_len = es.es_len - offset; +return IOMAP_DELALLOC ; + } + +/* Range starts with a hole */ + map->m_len = es.es_lblk - map->m_lblk; +return IOMAP_HOLE ; +}
This function would then be IMO better off to directly update 'iomap' as needed after ext4_set_iomap() sets hole there.
Honza
Quoted 133 lines
fs/ext4/inode.c +49
-54+ +static int ext4_iomap_begin_report (struct inode *inode,loff_t offset, +loff_t length,unsigned flags, +struct iomap *iomap) +{ +int ret; +u16 type =0 ; +struct ext4_map_blocks map; +u8 blkbits = inode->i_blkbits; +unsigned long first_block, last_block; + +if ((offset >> blkbits) >EXT4_MAX_LOGICAL_BLOCK ) +return -EINVAL ; + first_block = offset >> blkbits; + last_block =min_t (loff_t, (offset + length -1 ) >> blkbits, +EXT4_MAX_LOGICAL_BLOCK ); + +if (ext4_has_inline_data (inode)) { + ret =ext4_inline_data_iomap (inode, iomap); +if (ret != -EAGAIN ) { +if (ret ==0 && offset >= iomap->length) + ret = -ENOENT ; +return ret; + } + } + + map.m_lblk = first_block; + map.m_len = last_block = first_block +1 ; + ret =ext4_map_blocks (NULL , inode, &map,0 ); +if (ret <0 ) +return ret; +if (ret ==0 ) + type =ext4_iomap_check_delalloc (inode, &map); +return ext4_set_iomap (inode, iomap, type, first_block, &map); +} + +const struct iomap_ops ext4_iomap_report_ops = { + .iomap_begin = ext4_iomap_begin_report, +}; + static int ext4_iomap_alloc(struct inode *inode, unsigned flags, unsigned long first_block,@@ -3498,12 +3564,10 @@ static int ext4_iomap_alloc(struct inode *inode,static int ext4_iomap_begin (struct inode *inode,loff_t offset,loff_t length,unsigned flags,struct iomap *iomap) { -u16 type =0 ; -unsigned int blkbits = inode->i_blkbits; -unsigned long first_block, last_block; -struct ext4_map_blocks map; -bool delalloc = false;int ret; +struct ext4_map_blocks map; +u8 blkbits = inode->i_blkbits; +unsigned long first_block, last_block;if ((offset >> blkbits) >EXT4_MAX_LOGICAL_BLOCK )return -EINVAL ;@@ -3511,64 +3575,21 @@ static int ext4_iomap_begin(struct inode *inode, loff_t offset, loff_t length, last_block =min_t (loff_t, (offset + length -1 ) >> blkbits,EXT4_MAX_LOGICAL_BLOCK ); -if (flags &IOMAP_REPORT ) { -if (ext4_has_inline_data (inode)) { - ret =ext4_inline_data_iomap (inode, iomap); -if (ret != -EAGAIN ) { -if (ret ==0 && offset >= iomap->length) - ret = -ENOENT ; -return ret; - } - } - }else { -if (WARN_ON_ONCE (ext4_has_inline_data (inode))) -return -ERANGE ; - } +if (WARN_ON_ONCE (ext4_has_inline_data (inode))) +return -ERANGE ; map.m_lblk = first_block; map.m_len = last_block - first_block +1 ; -if (flags &IOMAP_REPORT ) { - ret =ext4_map_blocks (NULL , inode, &map,0 ); -if (ret <0 ) -return ret; - -if (ret ==0 ) { -ext4_lblk_t end = map.m_lblk + map.m_len -1 ; -struct extent_status es; - -ext4_es_find_extent_range (inode, &ext4_es_is_delayed, - map.m_lblk, end, &es); - -if (!es.es_len || es.es_lblk > end) { -/* entire range is a hole */ - }else if (es.es_lblk > map.m_lblk) { -/* range starts with a hole */ - map.m_len = es.es_lblk - map.m_lblk; - }else { -ext4_lblk_t offs =0 ; - -if (es.es_lblk < map.m_lblk) - offs = map.m_lblk - es.es_lblk; - map.m_lblk = es.es_lblk + offs; - map.m_len = es.es_len - offs; - delalloc = true; - } - } - }else if (flags &IOMAP_WRITE ) { +if (flags &IOMAP_WRITE ) ret =ext4_iomap_alloc (inode, flags, first_block, &map); - }else { +else ret =ext4_map_blocks (NULL , inode, &map,0 ); -if (ret <0 ) -return ret; - }if (ret <0 )return ret; - -if (!ret) - type = delalloc ?IOMAP_DELALLOC :IOMAP_HOLE ; -return ext4_set_iomap (inode, iomap, type, first_block, &map); +return ext4_set_iomap (inode, iomap, ret ?0 :IOMAP_HOLE , first_block, + &map); } static int ext4_iomap_end(struct inode *inode, loff_t offset, loff_t length,Signature · 1 line
2.20.1
Signature · 2 lines
Jan Kara <[email protected]> SUSE Labs, CR
Re: [PATCH v4 3/8] ext4: introduce new callback for IOMAP_REPORT operations
Quoted 4 lines · Jan Kara
On Thu 03-10-19 21:33:45, Matthew Bobrowski wrote:
The patch looks good to me. You can add:Reviewed-by Jan Kara <[email protected]>
Thanks Jan! :)
Quoted 1 line
It would just need small adjustments if you change patch 1 as I suggested:
I will await what you say in response to what my thoughts were aronud ext4_set_iomap() before doing any updates here.
Quoted 21 lines
Quoted 21 lines
fs/ext4/inode.c +21
-0+static u16 ext4_iomap_check_delalloc (struct inode *inode, +struct ext4_map_blocks *map) +{ +struct extent_status es; +ext4_lblk_t end = map->m_lblk + map->m_len -1 ; + +ext4_es_find_extent_range (inode, &ext4_es_is_delayed, map->m_lblk, + end, &es); + +/* Entire range is a hole */ +if (!es.es_len || es.es_lblk > end) +return IOMAP_HOLE ; +if (es.es_lblk <= map->m_lblk) { +ext4_lblk_t offset =0 ; + +if (es.es_lblk < map->m_lblk) + offset = map->m_lblk - es.es_lblk; + map->m_lblk = es.es_lblk + offset; + map->m_len = es.es_len - offset; +return IOMAP_DELALLOC ; + }
Quoted 8 lines
fs/ext4/inode.c static int ext4_set_iomap(struct inode *inode, struct iomap *iomap, u16 type, · line 3467
Quoted 5 lines
fs/ext4/inode.c +5
-0+ +/* Range starts with a hole */ + map->m_len = es.es_lblk - map->m_lblk; +return IOMAP_HOLE ; +}This function would then be IMO better off to directly update 'iomap' as needed after
ext4_set_iomap()sets hole there.
As mentioned in 1/8, it would be nice to leave all iomap setting up to ext4_set_iomap(), but if we're strongly against passing 'type', then I'm happy to change it and update this to pass an 'iomap'.
--<M>--
Re: [PATCH v4 3/8] ext4: introduce new callback for IOMAP_REPORT operations
In reply to Matthew BobrowskiQuoted 60 lines · Matthew Bobrowski
As part of
ext4_iomap_begin()cleanups and port across direct I/O path to make use of iomap infrastructure, we splitIOMAP_REPORToperations into a separate ->iomap_begin() handler.Signed-off-by Matthew Bobrowski <[email protected]>--- fs/ext4/ext4.h | 1 + fs/ext4/file.c | 6 ++- fs/ext4/inode.c | 129 ++++++++++++++++++++++++++++-------------------- 3 files changed, 80 insertions(+), 56 deletions(-)fs/ext4/ext4.h +1
-0@@ -3379,6 +3379,7 @@ static inline void ext4_clear_io_unwritten_flag(ext4_io_end_t *io_end) }extern const struct iomap_ops ext4_iomap_ops; +extern const struct iomap_ops ext4_iomap_report_ops;static inline int ext4_buffer_uptodate (struct buffer_head *bh) {fs/ext4/file.c +4
-2@@ -494,12 +494,14 @@ loff_t ext4_llseek(struct file *file, loff_t offset, int whence) maxbytes, i_size_read(inode));case SEEK_HOLE :inode_lock_shared (inode); - offset =iomap_seek_hole (inode, offset, &ext4_iomap_ops); + offset =iomap_seek_hole (inode, offset, + &ext4_iomap_report_ops);inode_unlock_shared (inode);break ;case SEEK_DATA :inode_lock_shared (inode); - offset =iomap_seek_data (inode, offset, &ext4_iomap_ops); + offset =iomap_seek_data (inode, offset, + &ext4_iomap_report_ops);inode_unlock_shared (inode);break ; }fs/ext4/inode.c +8
-0@@ -3439,6 +3439,72 @@ static int ext4_set_iomap(struct inode *inode, struct iomap *iomap, u16 type,return 0 ; } +static u16 ext4_iomap_check_delalloc (struct inode *inode, +struct ext4_map_blocks *map) +{ +struct extent_status es; +ext4_lblk_t end = map->m_lblk + map->m_len -1 ; + +ext4_es_find_extent_range (inode, &ext4_es_is_delayed, map->m_lblk, + end, &es);
fs/ext4/inode.c static int ext4_set_iomap(struct inode *inode, struct iomap *iomap, u16 type, · line 3459
Quoted 10 lines
fs/ext4/inode.c +10
-0+ +/* Entire range is a hole */ +if (!es.es_len || es.es_lblk > end) +return IOMAP_HOLE ; +if (es.es_lblk <= map->m_lblk) { +ext4_lblk_t offset =0 ; + +if (es.es_lblk < map->m_lblk) + offset = map->m_lblk - es.es_lblk; + map->m_lblk = es.es_lblk + offset;
This looks redundant no? map->m_lblk never changes actually. So this is not needed here.
Quoted 32 lines
fs/ext4/inode.c +32
-0+ map->m_len = es.es_len - offset; +return IOMAP_DELALLOC ; + } + +/* Range starts with a hole */ + map->m_len = es.es_lblk - map->m_lblk; +return IOMAP_HOLE ; +} + +static int ext4_iomap_begin_report (struct inode *inode,loff_t offset, +loff_t length,unsigned flags, +struct iomap *iomap) +{ +int ret; +u16 type =0 ; +struct ext4_map_blocks map; +u8 blkbits = inode->i_blkbits; +unsigned long first_block, last_block; + +if ((offset >> blkbits) >EXT4_MAX_LOGICAL_BLOCK ) +return -EINVAL ; + first_block = offset >> blkbits; + last_block =min_t (loff_t, (offset + length -1 ) >> blkbits, +EXT4_MAX_LOGICAL_BLOCK ); + +if (ext4_has_inline_data (inode)) { + ret =ext4_inline_data_iomap (inode, iomap); +if (ret != -EAGAIN ) { +if (ret ==0 && offset >= iomap->length) + ret = -ENOENT ; +return ret; + }
fs/ext4/inode.c static int ext4_set_iomap(struct inode *inode, struct iomap *iomap, u16 type, · line 3501
Quoted 10 lines
fs/ext4/inode.c +10
-0+ } + + map.m_lblk = first_block; + map.m_len = last_block = first_block +1 ; + ret =ext4_map_blocks (NULL , inode, &map,0 ); +if (ret <0 ) +return ret; +if (ret ==0 ) + type =ext4_iomap_check_delalloc (inode, &map); +return ext4_set_iomap (inode, iomap, type, first_block, &map);
We don't need to send first_block here. Since map->m_lblk is same as first_block.
Also with Jan comment, we don't even need 'type' parameter. Then we should be able to rename the function ext4_set_iomap ==> ext4_map_to_iomap. This better reflects what it is doing. Thoughts?
Quoted 97 lines
fs/ext4/inode.c +15
-54+} + +const struct iomap_ops ext4_iomap_report_ops = { + .iomap_begin = ext4_iomap_begin_report, +}; + static int ext4_iomap_alloc(struct inode *inode, unsigned flags, unsigned long first_block,@@ -3498,12 +3564,10 @@ static int ext4_iomap_alloc(struct inode *inode,static int ext4_iomap_begin (struct inode *inode,loff_t offset,loff_t length,unsigned flags,struct iomap *iomap) { -u16 type =0 ; -unsigned int blkbits = inode->i_blkbits; -unsigned long first_block, last_block; -struct ext4_map_blocks map; -bool delalloc = false;int ret; +struct ext4_map_blocks map; +u8 blkbits = inode->i_blkbits; +unsigned long first_block, last_block;if ((offset >> blkbits) >EXT4_MAX_LOGICAL_BLOCK )return -EINVAL ;@@ -3511,64 +3575,21 @@ static int ext4_iomap_begin(struct inode *inode, loff_t offset, loff_t length, last_block =min_t (loff_t, (offset + length -1 ) >> blkbits,EXT4_MAX_LOGICAL_BLOCK ); -if (flags &IOMAP_REPORT ) { -if (ext4_has_inline_data (inode)) { - ret =ext4_inline_data_iomap (inode, iomap); -if (ret != -EAGAIN ) { -if (ret ==0 && offset >= iomap->length) - ret = -ENOENT ; -return ret; - } - } - }else { -if (WARN_ON_ONCE (ext4_has_inline_data (inode))) -return -ERANGE ; - } +if (WARN_ON_ONCE (ext4_has_inline_data (inode))) +return -ERANGE ; map.m_lblk = first_block; map.m_len = last_block - first_block +1 ; -if (flags &IOMAP_REPORT ) { - ret =ext4_map_blocks (NULL , inode, &map,0 ); -if (ret <0 ) -return ret; - -if (ret ==0 ) { -ext4_lblk_t end = map.m_lblk + map.m_len -1 ; -struct extent_status es; - -ext4_es_find_extent_range (inode, &ext4_es_is_delayed, - map.m_lblk, end, &es); - -if (!es.es_len || es.es_lblk > end) { -/* entire range is a hole */ - }else if (es.es_lblk > map.m_lblk) { -/* range starts with a hole */ - map.m_len = es.es_lblk - map.m_lblk; - }else { -ext4_lblk_t offs =0 ; - -if (es.es_lblk < map.m_lblk) - offs = map.m_lblk - es.es_lblk; - map.m_lblk = es.es_lblk + offs; - map.m_len = es.es_len - offs; - delalloc = true; - } - } - }else if (flags &IOMAP_WRITE ) { +if (flags &IOMAP_WRITE ) ret =ext4_iomap_alloc (inode, flags, first_block, &map); - }else { +else ret =ext4_map_blocks (NULL , inode, &map,0 ); -if (ret <0 ) -return ret; - }if (ret <0 )return ret; - -if (!ret) - type = delalloc ?IOMAP_DELALLOC :IOMAP_HOLE ; -return ext4_set_iomap (inode, iomap, type, first_block, &map); +return ext4_set_iomap (inode, iomap, ret ?0 :IOMAP_HOLE , first_block, + &map); } static int ext4_iomap_end(struct inode *inode, loff_t offset, loff_t length,
Re: [PATCH v4 3/8] ext4: introduce new callback for IOMAP_REPORT operations
Quoted 12 lines · Ritesh Harjani
Quoted 12 lines
fs/ext4/inode.c +12
-0+static u16 ext4_iomap_check_delalloc (struct inode *inode, +struct ext4_map_blocks *map) +{ +struct extent_status es; +ext4_lblk_t end = map->m_lblk + map->m_len -1 ; + +ext4_es_find_extent_range (inode, &ext4_es_is_delayed, map->m_lblk, + end, &es); + +/* Entire range is a hole */ +if (!es.es_len || es.es_lblk > end) +return IOMAP_HOLE ;
Quoted 8 lines
fs/ext4/inode.c static int ext4_set_iomap(struct inode *inode, struct iomap *iomap, u16 type, · line 3459
Quoted 6 lines
fs/ext4/inode.c +6
-0+if (es.es_lblk <= map->m_lblk) { +ext4_lblk_t offset =0 ; + +if (es.es_lblk < map->m_lblk) + offset = map->m_lblk - es.es_lblk; + map->m_lblk = es.es_lblk + offset;This looks redundant no?
map->m_lblknever changes actually. So this is not needed here.
Well, it depends if map->m_lblk == es.es_lblk + offset prior to the assignment? If that's always true, then sure, it'd be redundant. But honestly, I don't know what the downstream effect would be if this was removed. I'd have to look at the code, perform some tests, and figure it out.
Quoted 6 lines
Quoted 6 lines
fs/ext4/inode.c +6
-0+ map.m_lblk = first_block; + map.m_len = last_block = first_block +1 ; + ret =ext4_map_blocks (NULL , inode, &map,0 ); +if (ret <0 ) +return ret; +if (ret ==0 )
Quoted 8 lines
fs/ext4/inode.c static int ext4_set_iomap(struct inode *inode, struct iomap *iomap, u16 type, · line 3501
Quoted 2 lines
fs/ext4/inode.c +2
-0+ type =ext4_iomap_check_delalloc (inode, &map); +return ext4_set_iomap (inode, iomap, type, first_block, &map);We don't need to send
first_blockhere. Sincemap->m_lblkis same asfirst_block.
Also with Jan comment, we don't even need 'type' parameter. Then we should be able to rename the functionext4_set_iomap==>ext4_map_to_iomap. This better reflects what it is doing. Thoughts?
Depends on what we conclude in 1/8. :)
I'm for removing 'first_block', but still not convinced removing 'type' is heading down the right track if I were to forward think a little.
--<M>--
Re: [PATCH v4 3/8] ext4: introduce new callback for IOMAP_REPORT operations
Quoted 22 lines · Matthew Bobrowski
Quoted 12 lines · Ritesh Harjani
Quoted 12 lines
fs/ext4/inode.c +12
-0+static u16 ext4_iomap_check_delalloc (struct inode *inode, +struct ext4_map_blocks *map) +{ +struct extent_status es; +ext4_lblk_t end = map->m_lblk + map->m_len -1 ; + +ext4_es_find_extent_range (inode, &ext4_es_is_delayed, map->m_lblk, + end, &es); + +/* Entire range is a hole */ +if (!es.es_len || es.es_lblk > end) +return IOMAP_HOLE ;Quoted 8 lines
fs/ext4/inode.c static int ext4_set_iomap(struct inode *inode, struct iomap *iomap, u16 type, · line 3459
Quoted 6 lines
fs/ext4/inode.c +6
-0+if (es.es_lblk <= map->m_lblk) { +ext4_lblk_t offset =0 ; + +if (es.es_lblk < map->m_lblk) + offset = map->m_lblk - es.es_lblk; + map->m_lblk = es.es_lblk + offset;This looks redundant no?
map->m_lblknever changes actually. So this is not needed here.
Quoted 5 lines
Well, it depends if
map->m_lblk== es.es_lblk + offset prior to the assignment? If that's always true, then sure, it'd be redundant. But honestly, I don't know what the downstream effect would be if this was removed. I'd have to look at the code, perform some tests, and figure it out.
<snip>
3334 if (es.es_lblk <= map->m_lblk) {
3335 ext4_lblk_t offset = 0;
3336
3337 if (es.es_lblk < map->m_lblk)
3338 offset = map->m_lblk - es.es_lblk;
3339 map->m_lblk = es.es_lblk + offset; 3340 map->m_len = es.es_len - offset; 3341 return IOMAP_DELALLOC;
3342 }
I saw it this way-
In condition "if (es.es_lblk <= map->m_lblk)" there are 2 cases.
Case 1: es.es_lblk is equal to map->m_lblk (equality)
For this case, "offset" will remain 0.
So map->lblk = es.es_lblk + 0 (but since es.es_lblk is same asmap->m_lblk in equality case, so it is redundant).
Case 2: es.es_lblk < map->m_lblk (less than)
In this case "offset = map->m_lblk - es.es_lblk"
Now replacing this val of offset in "map->m_lblk = es.es_lblk + offset" map->m_lblk = es.es_lblk + map->m_lblk - es.es_lblk
which again is map->m_lblk = map->m_lblk - again redundant.
What did I miss?
But sure feel free to test as per your convenience.
Quoted 16 lines
Quoted 15 lines
fs/ext4/inode.c static int ext4_set_iomap(struct inode *inode, struct iomap *iomap, u16 type, · line 3501
Quoted 9 lines
fs/ext4/inode.c +8
-0+ map.m_lblk = first_block; + map.m_len = last_block = first_block +1 ; + ret =ext4_map_blocks (NULL , inode, &map,0 ); +if (ret <0 ) +return ret; +if (ret ==0 ) + type =ext4_iomap_check_delalloc (inode, &map); +return ext4_set_iomap (inode, iomap, type, first_block, &map);We don't need to send
first_blockhere. Sincemap->m_lblkis same asfirst_block.
Also with Jan comment, we don't even need 'type' parameter. Then we should be able to rename the functionext4_set_iomap==>ext4_map_to_iomap. This better reflects what it is doing. Thoughts?
Quoted 5 lines
Depends on what we conclude in 1/8. :)
I'm for removing '
first_block', but still not convinced removing 'type' is heading down the right track if I were to forward think a little.
Only once you are convinced that map->m_lblk will not change even in function ext4_iomap_check_delalloc(), then only you should drop "first_block" argument from ext4_set_iomap.
Please check above comments once.
-ritesh
PATCH v4 4/8 ext4: introduce direct I/O read path using iomap infrastructure
In reply to Matthew BobrowskiThis patch introduces a new direct I/O read path that makes use of the iomap infrastructure.
The new function ext4_dio_read_iter() is responsible for calling into the iomap infrastructure via iomap_dio_rw(). If the read operation being performed on the inode does not pass the preliminary checks performed within ext4_dio_supported(), then we simply fallback to buffered I/O in order to fulfil the request.
Existing direct I/O read buffer_head code has been removed as it's now redundant.
--- fs/ext4/file.c | 58 +++++++++++++++++++++++++++++++++++++++++++++---- fs/ext4/inode.c | 32 +-------------------------- 2 files changed, 55 insertions(+), 35 deletions(-)
fs/ext4/file.c +54 -4
@@ -34,6 +34,53 @@#include "xattr.h" #include "acl.h" +static bool ext4_dio_supported (struct inode *inode) +{ +if (IS_ENABLED (CONFIG_FS_ENCRYPTION ) &&IS_ENCRYPTED (inode)) +return false; +if (fsverity_active (inode)) +return false; +if (ext4_should_journal_data (inode)) +return false; +if (ext4_has_inline_data (inode)) +return false; +return true; +} + +static ssize_t ext4_dio_read_iter (struct kiocb *iocb,struct iov_iter *to) +{ +ssize_t ret; +struct inode *inode =file_inode (iocb->ki_filp); + +/* +* Get exclusion from truncate and other inode operations. +*/ +if (!inode_trylock_shared (inode)) { +if (iocb->ki_flags &IOCB_NOWAIT ) +return -EAGAIN ; +inode_lock_shared (inode); + } + +if (!ext4_dio_supported (inode)) { +inode_unlock_shared (inode); +/* +* Fallback to buffered I/O if the operation being +* performed on the inode is not supported by direct +* I/O. The IOCB_DIRECT flag needs to be cleared here +* in order to ensure that the direct I/O path withiin +* generic_file_read_iter() is not taken. +*/ + iocb->ki_flags &= ~IOCB_DIRECT ; +return generic_file_read_iter (iocb, to); + } + + ret =iomap_dio_rw (iocb, to, &ext4_iomap_ops,NULL ); +inode_unlock_shared (inode); + +file_accessed (iocb->ki_filp); +return ret; +} +#ifdef CONFIG_FS_DAX static ssize_t ext4_dax_read_iter (struct kiocb *iocb,struct iov_iter *to) {
@@ -64,16 +111,19 @@ static ssize_t ext4_dax_read_iter(struct kiocb *iocb, struct iov_iter *to)static ssize_t ext4_file_read_iter (struct kiocb *iocb,struct iov_iter *to) { -if (unlikely (ext4_forced_shutdown (EXT4_SB (file_inode (iocb->ki_filp)->i_sb)))) +struct inode *inode =file_inode (iocb->ki_filp); + +if (unlikely (ext4_forced_shutdown (EXT4_SB (inode->i_sb))))return -EIO ;if (!iov_iter_count (to))return 0 ;/* skip atime */ -#ifdef CONFIG_FS_DAX -if (IS_DAX (file_inode (iocb->ki_filp))) +if (IS_DAX (inode))return ext4_dax_read_iter (iocb, to); -#endif + +if (iocb->ki_flags &IOCB_DIRECT ) +return ext4_dio_read_iter (iocb, to);return generic_file_read_iter (iocb, to); }
fs/ext4/inode.c +1 -31
@@ -863,9 +863,6 @@ int ext4_dio_get_block(struct inode *inode, sector_t iblock, {/* We don't expect handle for direct IO */ WARN_ON_ONCE (ext4_journal_current_handle ()); - -if (!create) -return _ext4_get_block (inode, iblock, bh,0 );return ext4_get_block_trans (inode, iblock, bh,EXT4_GET_BLOCKS_CREATE ); }
@@ -3855,30 +3852,6 @@ static ssize_t ext4_direct_IO_write(struct kiocb *iocb, struct iov_iter *iter)return ret; } -static ssize_t ext4_direct_IO_read (struct kiocb *iocb,struct iov_iter *iter) -{ -struct address_space *mapping = iocb->ki_filp->f_mapping; -struct inode *inode = mapping->host; -size_t count =iov_iter_count (iter); -ssize_t ret; - -/* -* Shared inode_lock is enough for us - it protects against concurrent -* writes & truncates and since we take care of writing back page cache, -* we are protected against page writeback as well. -*/ -inode_lock_shared (inode); - ret =filemap_write_and_wait_range (mapping, iocb->ki_pos, - iocb->ki_pos + count -1 ); -if (ret) - goto out_unlock; - ret =__blockdev_direct_IO (iocb, inode, inode->i_sb->s_bdev, - iter, ext4_dio_get_block,NULL ,NULL ,0 ); -out_unlock: -inode_unlock_shared (inode); -return ret; -} -static ssize_t ext4_direct_IO (struct kiocb *iocb,struct iov_iter *iter) {struct file *file = iocb->ki_filp;
@@ -3905,10 +3878,7 @@ static ssize_t ext4_direct_IO(struct kiocb *iocb, struct iov_iter *iter)return 0 ;trace_ext4_direct_IO_enter (inode, offset, count,iov_iter_rw (iter)); -if (iov_iter_rw (iter) ==READ ) - ret =ext4_direct_IO_read (iocb, iter); -else - ret =ext4_direct_IO_write (iocb, iter); + ret =ext4_direct_IO_write (iocb, iter);trace_ext4_direct_IO_exit (inode, offset, count,iov_iter_rw (iter), ret);return ret; }
Signature · 1 line
2.20.1
Re: [PATCH v4 4/8] ext4: introduce direct I/O read path using iomap infrastructure
Quoted 9 lines · Matthew Bobrowski
This patch introduces a new direct I/O read path that makes use of the iomap infrastructure.
The new function
ext4_dio_read_iter()is responsible for calling into the iomap infrastructure viaiomap_dio_rw(). If the read operation being performed on the inode does not pass the preliminary checks performed withinext4_dio_supported(), then we simply fallback to buffered I/O in order to fulfil the request.
Quoted 4 lines
Existing direct I/O read
buffer_headcode has been removed as it's now redundant.Signed-off-by Matthew Bobrowski <[email protected]>
The patch looks good to me. Just one small nit below. With that fixed, you can add:
fs/ext4/file.c line 62
Quoted 8 lines
fs/ext4/file.c +8
-0+/* +* Get exclusion from truncate and other inode operations. +*/ +if (!inode_trylock_shared (inode)) { +if (iocb->ki_flags &IOCB_NOWAIT ) +return -EAGAIN ; +inode_lock_shared (inode); + }
I've noticed here you actually introduce new trylock pattern - previously we had unconditional inode_lock_shared() in ext4_direct_IO_read(). So the cleanest would be to just use unconditional inode_lock_shared() here and then fixup IOCB_NOWAIT handling (I agree that was missing in the original code) in a separate patch. And the pattern should rather look like:
if (iocb->ki_flags & IOCB_NOWAIT) {
if (!inode_trylock_shared(inode))
return -EAGAIN;
} else {
inode_lock_shared(inode);
}to avoid two atomical operations instead of one in the fast path. No need to repeat old mistakes when we know better :).
Honza
Signature · 2 lines
Jan Kara <[email protected]> SUSE Labs, CR
Re: [PATCH v4 4/8] ext4: introduce direct I/O read path using iomap infrastructure
Quoted 13 lines · Jan Kara
Quoted 12 lines · Matthew Bobrowski
This patch introduces a new direct I/O read path that makes use of the iomap infrastructure.
The new function
ext4_dio_read_iter()is responsible for calling into the iomap infrastructure viaiomap_dio_rw(). If the read operation being performed on the inode does not pass the preliminary checks performed withinext4_dio_supported(), then we simply fallback to buffered I/O in order to fulfil the request.Existing direct I/O read
buffer_headcode has been removed as it's now redundant.
Quoted 6 lines
Quoted 1 line
Signed-off-by Matthew Bobrowski <[email protected]>The patch looks good to me. Just one small nit below. With that fixed, you can add:
Reviewed-by Jan Kara <[email protected]>
Cool, I'll fix it!
Quoted 6 lines
Quoted 6 lines
fs/ext4/file.c +6
-0+/* +* Get exclusion from truncate and other inode operations. +*/ +if (!inode_trylock_shared (inode)) { +if (iocb->ki_flags &IOCB_NOWAIT ) +return -EAGAIN ;
Quoted 8 lines
Review
Quoted 2 lines
(quoted diff) +2
-0+ inode_lock_shared(inode); + }I've noticed here you actually introduce new trylock pattern - previously we had unconditional
inode_lock_shared()inext4_direct_IO_read(). So the cleanest would be to just use unconditionalinode_lock_shared()here and then fixupIOCB_NOWAIThandling (I agree that was missing in the original code) in a separate patch.
Right, so I will just have an unconditional call to inode_lock_shared() and in the patch that follows I will fix it up to apply the new pattern.
Quoted 11 lines
And the pattern should rather look like:
if (iocb->ki_flags & IOCB_NOWAIT) { if (!inode_trylock_shared(inode)) return -EAGAIN; } else { inode_lock_shared(inode); }to avoid two atomical operations instead of one in the fast path. No need to repeat old mistakes when we know better :).
Yes, also agree.
--<M>--
Re: [PATCH v4 4/8] ext4: introduce direct I/O read path using iomap infrastructure
In reply to Matthew BobrowskiQuoted 42 lines · Matthew Bobrowski
This patch introduces a new direct I/O read path that makes use of the iomap infrastructure.
The new function
ext4_dio_read_iter()is responsible for calling into the iomap infrastructure viaiomap_dio_rw(). If the read operation being performed on the inode does not pass the preliminary checks performed withinext4_dio_supported(), then we simply fallback to buffered I/O in order to fulfil the request.Existing direct I/O read
buffer_headcode has been removed as it's now redundant.Signed-off-by Matthew Bobrowski <[email protected]>--- fs/ext4/file.c | 58 +++++++++++++++++++++++++++++++++++++++++++++---- fs/ext4/inode.c | 32 +-------------------------- 2 files changed, 55 insertions(+), 35 deletions(-)fs/ext4/file.c +16
-0@@ -34,6 +34,53 @@#include "xattr.h" #include "acl.h" +static bool ext4_dio_supported (struct inode *inode) +{ +if (IS_ENABLED (CONFIG_FS_ENCRYPTION ) &&IS_ENCRYPTED (inode)) +return false; +if (fsverity_active (inode)) +return false; +if (ext4_should_journal_data (inode)) +return false; +if (ext4_has_inline_data (inode)) +return false; +return true; +} + +static ssize_t ext4_dio_read_iter (struct kiocb *iocb,struct iov_iter *to) +{ +ssize_t ret;
fs/ext4/file.c line 62
Quoted 10 lines
fs/ext4/file.c +10
-0+struct inode *inode =file_inode (iocb->ki_filp); + +/* +* Get exclusion from truncate and other inode operations. +*/ +if (!inode_trylock_shared (inode)) { +if (iocb->ki_flags &IOCB_NOWAIT ) +return -EAGAIN ; +inode_lock_shared (inode); + }
Same comments here.
Let's follow as per the discussion here
https://patchwork.kernel.org/patch/11141577/
Quoted 106 lines
fs/ext4/file.c +28
-4+ +if (!ext4_dio_supported (inode)) { +inode_unlock_shared (inode); +/* +* Fallback to buffered I/O if the operation being +* performed on the inode is not supported by direct +* I/O. The IOCB_DIRECT flag needs to be cleared here +* in order to ensure that the direct I/O path withiin +* generic_file_read_iter() is not taken. +*/ + iocb->ki_flags &= ~IOCB_DIRECT ; +return generic_file_read_iter (iocb, to); + } + + ret =iomap_dio_rw (iocb, to, &ext4_iomap_ops,NULL ); +inode_unlock_shared (inode); + +file_accessed (iocb->ki_filp); +return ret; +} +#ifdef CONFIG_FS_DAX static ssize_t ext4_dax_read_iter (struct kiocb *iocb,struct iov_iter *to) {@@ -64,16 +111,19 @@ static ssize_t ext4_dax_read_iter(struct kiocb *iocb, struct iov_iter *to)static ssize_t ext4_file_read_iter (struct kiocb *iocb,struct iov_iter *to) { -if (unlikely (ext4_forced_shutdown (EXT4_SB (file_inode (iocb->ki_filp)->i_sb)))) +struct inode *inode =file_inode (iocb->ki_filp); + +if (unlikely (ext4_forced_shutdown (EXT4_SB (inode->i_sb))))return -EIO ;if (!iov_iter_count (to))return 0 ;/* skip atime */ -#ifdef CONFIG_FS_DAX -if (IS_DAX (file_inode (iocb->ki_filp))) +if (IS_DAX (inode))return ext4_dax_read_iter (iocb, to); -#endif + +if (iocb->ki_flags &IOCB_DIRECT ) +return ext4_dio_read_iter (iocb, to);return generic_file_read_iter (iocb, to); }fs/ext4/inode.c +1
-31@@ -863,9 +863,6 @@ int ext4_dio_get_block(struct inode *inode, sector_t iblock, {/* We don't expect handle for direct IO */ WARN_ON_ONCE (ext4_journal_current_handle ()); - -if (!create) -return _ext4_get_block (inode, iblock, bh,0 );return ext4_get_block_trans (inode, iblock, bh,EXT4_GET_BLOCKS_CREATE ); }@@ -3855,30 +3852,6 @@ static ssize_t ext4_direct_IO_write(struct kiocb *iocb, struct iov_iter *iter)return ret; } -static ssize_t ext4_direct_IO_read (struct kiocb *iocb,struct iov_iter *iter) -{ -struct address_space *mapping = iocb->ki_filp->f_mapping; -struct inode *inode = mapping->host; -size_t count =iov_iter_count (iter); -ssize_t ret; - -/* -* Shared inode_lock is enough for us - it protects against concurrent -* writes & truncates and since we take care of writing back page cache, -* we are protected against page writeback as well. -*/ -inode_lock_shared (inode); - ret =filemap_write_and_wait_range (mapping, iocb->ki_pos, - iocb->ki_pos + count -1 ); -if (ret) - goto out_unlock; - ret =__blockdev_direct_IO (iocb, inode, inode->i_sb->s_bdev, - iter, ext4_dio_get_block,NULL ,NULL ,0 ); -out_unlock: -inode_unlock_shared (inode); -return ret; -} -static ssize_t ext4_direct_IO (struct kiocb *iocb,struct iov_iter *iter) {struct file *file = iocb->ki_filp;@@ -3905,10 +3878,7 @@ static ssize_t ext4_direct_IO(struct kiocb *iocb, struct iov_iter *iter)return 0 ;trace_ext4_direct_IO_enter (inode, offset, count,iov_iter_rw (iter)); -if (iov_iter_rw (iter) ==READ ) - ret =ext4_direct_IO_read (iocb, iter); -else - ret =ext4_direct_IO_write (iocb, iter); + ret =ext4_direct_IO_write (iocb, iter);trace_ext4_direct_IO_exit (inode, offset, count,iov_iter_rw (iter), ret);return ret; }
PATCH v4 5/8 ext4: move inode extension/truncate code out from ->iomap_end() callback
In reply to Matthew BobrowskiIn preparation for implementing the iomap direct I/O write path modifications, the inode extension/truncate code needs to be moved out from ext4_iomap_end(). For direct I/O, if the current code remained within ext4_iomap_end() it would behave incorrectly. Updating the inode size prior to converting unwritten extents to written extents will potentially allow a racing direct I/O read operation to find unwritten extents before they've been correctly converted.
The inode extension/truncate code has been moved out into a new helper ext4_handle_inode_extension(). This function has been designed so that it can be used by both DAX and direct I/O paths.
--- fs/ext4/file.c | 79 ++++++++++++++++++++++++++++++++++++++++++++++++- fs/ext4/inode.c | 48 +----------------------------- 2 files changed, 79 insertions(+), 48 deletions(-)
fs/ext4/file.c +78 -1
@@ -33,6 +33,7 @@#include "ext4_jbd2.h" #include "xattr.h" #include "acl.h" +#include "truncate.h" static bool ext4_dio_supported (struct inode *inode) {
@@ -233,12 +234,82 @@ static ssize_t ext4_write_checks(struct kiocb *iocb, struct iov_iter *from)return iov_iter_count (from); } +static int ext4_handle_inode_extension (struct inode *inode,loff_t offset, +ssize_t written,size_t count) +{ +int ret =0 ; +handle_t *handle; +bool truncate = false; +u8 blkbits = inode->i_blkbits; +ext4_lblk_t written_blk, end_blk; + +/* +* Note that EXT4_I(inode)->i_disksize can get extended up to +* inode->i_size while the IO was running due to writeback of +* delalloc blocks. But the code in ext4_iomap_alloc() is careful +* to use zeroed / unwritten extents if this is possible and thus +* we won't leave uninitialized blocks in a file even if we didn't +* succeed in writing as much as we planned. +*/ +WARN_ON_ONCE (i_size_read (inode) <EXT4_I (inode)->i_disksize); +if (offset + count <=EXT4_I (inode)->i_disksize) +return written <0 ? written :0 ; + +if (written <0 ) { + ret = written; + goto truncate; + } + + handle =ext4_journal_start (inode,EXT4_HT_INODE ,2 ); +if (IS_ERR (handle)) { + ret =PTR_ERR (handle); + goto truncate; + } + +if (ext4_update_inode_size (inode, offset + written)) +ext4_mark_inode_dirty (handle, inode); + +/* +* We may need to truncate allocated but not written blocks +* beyond EOF. +*/ + written_blk =ALIGN (offset + written,1 << blkbits); + end_blk =ALIGN (offset + count,1 << blkbits); +if (written_blk < end_blk &&ext4_can_truncate (inode)) + truncate = true; + +/* +* Remove the inode from the orphan list if it has been +* extended and everything went OK. +*/ +if (!truncate && inode->i_nlink) +ext4_orphan_del (handle, inode); +ext4_journal_stop (handle); + +if (truncate) { +truncate: +ext4_truncate_failed_write (inode); +/* +* If the truncate operation failed early, then the +* inode may still be on the orphan list. In that +* case, we need to try remove the inode from the +* in-memory linked list. +*/ +if (inode->i_nlink) +ext4_orphan_del (NULL , inode); + } +return ret; +} +#ifdef CONFIG_FS_DAX static ssize_t ext4_dax_write_iter (struct kiocb *iocb,struct iov_iter *from) { -struct inode *inode =file_inode (iocb->ki_filp); +int error;ssize_t ret; +size_t count; +loff_t offset; +struct inode *inode =file_inode (iocb->ki_filp);if (!inode_trylock (inode)) {if (iocb->ki_flags &IOCB_NOWAIT )
@@ -255,7 +326,13 @@ ext4_dax_write_iter(struct kiocb *iocb, struct iov_iter *from)if (ret) goto out; + offset = iocb->ki_pos; + count =iov_iter_count (from); ret =dax_iomap_rw (iocb, from, &ext4_iomap_ops); + + error =ext4_handle_inode_extension (inode, offset, ret, count); +if (error) + ret = error; out:inode_unlock (inode);if (ret >0 )
fs/ext4/inode.c +1 -47
54 lines not on this page · raw message
Signature · 1 line
2.20.1
Re: [PATCH v4 5/8] ext4: move inode extension/truncate code out from ->iomap_end() callback
Quoted 8 lines · Matthew Bobrowski
In preparation for implementing the iomap direct I/O write path modifications, the inode extension/truncate code needs to be moved out from
ext4_iomap_end(). For direct I/O, if the current code remained withinext4_iomap_end()it would behave incorrectly. Updating the inode size prior to converting unwritten extents to written extents will potentially allow a racing direct I/O read operation to find unwritten extents before they've been correctly converted.
Quoted 5 lines
The inode extension/truncate code has been moved out into a new helper
ext4_handle_inode_extension(). This function has been designed so that it can be used by both DAX and direct I/O paths.Signed-off-by Matthew Bobrowski <[email protected]>
Looks good to me. Fell free to add:
Just small nits below:
fs/ext4/file.c static ssize_t ext4_write_checks(struct kiocb *iocb, struct iov_iter *from) · line 240
Quoted 4 lines
fs/ext4/file.c +4
-0+static int ext4_handle_inode_extension (struct inode *inode,loff_t offset, +ssize_t written,size_t count) +{ +int ret =0 ;
I think both the function and callsites may be slightly simpler if you let the function return 'written' or error (not 0 or error). But I'll leave that decision upto you.
fs/ext4/file.c static ssize_t ext4_write_checks(struct kiocb *iocb, struct iov_iter *from) · line 253
Quoted 13 lines
fs/ext4/file.c +13
-0+handle_t *handle; +bool truncate = false; +u8 blkbits = inode->i_blkbits; +ext4_lblk_t written_blk, end_blk; + +/* +* Note that EXT4_I(inode)->i_disksize can get extended up to +* inode->i_size while the IO was running due to writeback of +* delalloc blocks. But the code in ext4_iomap_alloc() is careful +* to use zeroed / unwritten extents if this is possible and thus +* we won't leave uninitialized blocks in a file even if we didn't +* succeed in writing as much as we planned. +*/
Whitespace damaged here...
Honza
Signature · 2 lines
Jan Kara <[email protected]> SUSE Labs, CR
Re: [PATCH v4 5/8] ext4: move inode extension/truncate code out from ->iomap_end() callback
Quoted 4 lines · Jan Kara
On Thu 03-10-19 21:34:18, Matthew Bobrowski wrote:
Looks good to me. Fell free to add:Reviewed-by Jan Kara <[email protected]>
Thanks Jan!
Quoted 10 lines
Just small nits below:
fs/ext4/file.c static ssize_t ext4_write_checks(struct kiocb *iocb, struct iov_iter *from) · line 240
Quoted 4 lines
fs/ext4/file.c +4
-0+static int ext4_handle_inode_extension (struct inode *inode,loff_t offset, +ssize_t written,size_t count) +{ +int ret =0 ;I think both the function and callsites may be slightly simpler if you let the function return 'written' or error (not 0 or error). But I'll leave that decision upto you.
Hm, don't we actually need to return 0 for success cases so that iomap_dio_complete() behaves correctly i.e. increments iocb->ki_pos, etc?
Quoted 7 lines
Quoted 7 lines
fs/ext4/file.c +7
-0+handle_t *handle; +bool truncate = false; +u8 blkbits = inode->i_blkbits; +ext4_lblk_t written_blk, end_blk; + +/* +* Note that EXT4_I(inode)->i_disksize can get extended up to
Quoted 8 lines
fs/ext4/file.c static ssize_t ext4_write_checks(struct kiocb *iocb, struct iov_iter *from) · line 253
Quoted 6 lines
fs/ext4/file.c +6
-0+* inode->i_size while the IO was running due to writeback of +* delalloc blocks. But the code in ext4_iomap_alloc() is careful +* to use zeroed / unwritten extents if this is possible and thus +* we won't leave uninitialized blocks in a file even if we didn't +* succeed in writing as much as we planned. +*/ Whitespace damaged here...
I'll fix this.
--<M>--
Jan Kara
reviewerRe: [PATCH v4 5/8] ext4: move inode extension/truncate code out from ->iomap_end() callback
Quoted 11 lines · Matthew Bobrowski
Quoted 10 lines
Just small nits below:
fs/ext4/file.c static ssize_t ext4_write_checks(struct kiocb *iocb, struct iov_iter *from) · line 240
Quoted 4 lines
fs/ext4/file.c +4
-0+static int ext4_handle_inode_extension (struct inode *inode,loff_t offset, +ssize_t written,size_t count) +{ +int ret =0 ;I think both the function and callsites may be slightly simpler if you let the function return 'written' or error (not 0 or error). But I'll leave that decision upto you.
Quoted 3 lines
Hm, don't we actually need to return 0 for success cases so that
iomap_dio_complete()behaves correctly i.e. incrementsiocb->ki_pos, etc?
Correct, iomap_dio_complete() expects 0 on success. So if we keep calling ext4_handle_inode_extension() from ->end_io handler, we'd need some specialcasing there and I agree that changing ext4_handle_inode_extension() return convention isn't then very beneficial. If we stop calling ext4_handle_inode_extension() from ->end_io handler (patch 8/8 discussion pending), then the change would be a clear win.
Honza
Signature · 2 lines
Jan Kara <[email protected]> SUSE Labs, CR
Re: [PATCH v4 5/8] ext4: move inode extension/truncate code out from ->iomap_end() callback
Quoted 16 lines · Jan Kara
Quoted 11 lines · Matthew Bobrowski
Quoted 10 lines
Just small nits below:
fs/ext4/file.c static ssize_t ext4_write_checks(struct kiocb *iocb, struct iov_iter *from) · line 240
Quoted 4 lines
fs/ext4/file.c +4
-0+static int ext4_handle_inode_extension (struct inode *inode,loff_t offset, +ssize_t written,size_t count) +{ +int ret =0 ;I think both the function and callsites may be slightly simpler if you let the function return 'written' or error (not 0 or error). But I'll leave that decision upto you.
Quoted 3 lines
Hm, don't we actually need to return 0 for success cases so that
iomap_dio_complete()behaves correctly i.e. incrementsiocb->ki_pos, etc?
Quoted 6 lines
Correct,
iomap_dio_complete()expects 0 on success. So if we keep callingext4_handle_inode_extension()from ->end_io handler, we'd need some specialcasing there and I agree that changingext4_handle_inode_extension()return convention isn't then very beneficial. If we stop callingext4_handle_inode_extension()from ->end_io handler (patch 8/8 discussion pending), then the change would be a clear win.
Agreed. Well, I think we've got some movement in the right direction in 8/8, so it looks like changing up the return values is what we'll go ahead with.
--<M>--
Re: [PATCH v4 5/8] ext4: move inode extension/truncate code out from ->iomap_end() callback
In reply to Matthew BobrowskiQuoted 8 lines · Matthew Bobrowski
In preparation for implementing the iomap direct I/O write path modifications, the inode extension/truncate code needs to be moved out from
ext4_iomap_end(). For direct I/O, if the current code remained withinext4_iomap_end()it would behave incorrectly. Updating the inode size prior to converting unwritten extents to written extents will potentially allow a racing direct I/O read operation to find unwritten extents before they've been correctly converted.
Quoted 5 lines
The inode extension/truncate code has been moved out into a new helper
ext4_handle_inode_extension(). This function has been designed so that it can be used by both DAX and direct I/O paths.Signed-off-by Matthew Bobrowski <[email protected]>
checkpatch shows some whitespaces error in your comments in this patch.
But apart from that, patch looks good to me. You may add:
Quoted 175 lines
--- fs/ext4/file.c | 79 ++++++++++++++++++++++++++++++++++++++++++++++++- fs/ext4/inode.c | 48 +----------------------------- 2 files changed, 79 insertions(+), 48 deletions(-)fs/ext4/file.c +78
-1@@ -33,6 +33,7 @@#include "ext4_jbd2.h" #include "xattr.h" #include "acl.h" +#include "truncate.h" static bool ext4_dio_supported (struct inode *inode) {@@ -233,12 +234,82 @@ static ssize_t ext4_write_checks(struct kiocb *iocb, struct iov_iter *from)return iov_iter_count (from); } +static int ext4_handle_inode_extension (struct inode *inode,loff_t offset, +ssize_t written,size_t count) +{ +int ret =0 ; +handle_t *handle; +bool truncate = false; +u8 blkbits = inode->i_blkbits; +ext4_lblk_t written_blk, end_blk; + +/* +* Note that EXT4_I(inode)->i_disksize can get extended up to +* inode->i_size while the IO was running due to writeback of +* delalloc blocks. But the code in ext4_iomap_alloc() is careful +* to use zeroed / unwritten extents if this is possible and thus +* we won't leave uninitialized blocks in a file even if we didn't +* succeed in writing as much as we planned. +*/ +WARN_ON_ONCE (i_size_read (inode) <EXT4_I (inode)->i_disksize); +if (offset + count <=EXT4_I (inode)->i_disksize) +return written <0 ? written :0 ; + +if (written <0 ) { + ret = written; + goto truncate; + } + + handle =ext4_journal_start (inode,EXT4_HT_INODE ,2 ); +if (IS_ERR (handle)) { + ret =PTR_ERR (handle); + goto truncate; + } + +if (ext4_update_inode_size (inode, offset + written)) +ext4_mark_inode_dirty (handle, inode); + +/* +* We may need to truncate allocated but not written blocks +* beyond EOF. +*/ + written_blk =ALIGN (offset + written,1 << blkbits); + end_blk =ALIGN (offset + count,1 << blkbits); +if (written_blk < end_blk &&ext4_can_truncate (inode)) + truncate = true; + +/* +* Remove the inode from the orphan list if it has been +* extended and everything went OK. +*/ +if (!truncate && inode->i_nlink) +ext4_orphan_del (handle, inode); +ext4_journal_stop (handle); + +if (truncate) { +truncate: +ext4_truncate_failed_write (inode); +/* +* If the truncate operation failed early, then the +* inode may still be on the orphan list. In that +* case, we need to try remove the inode from the +* in-memory linked list. +*/ +if (inode->i_nlink) +ext4_orphan_del (NULL , inode); + } +return ret; +} +#ifdef CONFIG_FS_DAX static ssize_t ext4_dax_write_iter (struct kiocb *iocb,struct iov_iter *from) { -struct inode *inode =file_inode (iocb->ki_filp); +int error;ssize_t ret; +size_t count; +loff_t offset; +struct inode *inode =file_inode (iocb->ki_filp);if (!inode_trylock (inode)) {if (iocb->ki_flags &IOCB_NOWAIT )@@ -255,7 +326,13 @@ ext4_dax_write_iter(struct kiocb *iocb, struct iov_iter *from)if (ret) goto out; + offset = iocb->ki_pos; + count =iov_iter_count (from); ret =dax_iomap_rw (iocb, from, &ext4_iomap_ops); + + error =ext4_handle_inode_extension (inode, offset, ret, count); +if (error) + ret = error; out:inode_unlock (inode);if (ret >0 )fs/ext4/inode.c +1
-47@@ -3592,53 +3592,7 @@ static int ext4_iomap_begin(struct inode *inode, loff_t offset, loff_t length,static int ext4_iomap_end (struct inode *inode,loff_t offset,loff_t length,ssize_t written,unsigned flags,struct iomap *iomap) { -int ret =0 ; -handle_t *handle; -int blkbits = inode->i_blkbits; -bool truncate = false; - -if (!(flags &IOMAP_WRITE ) || (flags &IOMAP_FAULT )) -return 0 ; - - handle =ext4_journal_start (inode,EXT4_HT_INODE ,2 ); -if (IS_ERR (handle)) { - ret =PTR_ERR (handle); - goto orphan_del; - } -if (ext4_update_inode_size (inode, offset + written)) -ext4_mark_inode_dirty (handle, inode); -/* -* We may need to truncate allocated but not written blocks beyond EOF. -*/ -if (iomap->offset + iomap->length > -ALIGN (inode->i_size,1 << blkbits)) { -ext4_lblk_t written_blk, end_blk; - - written_blk = (offset + written) >> blkbits; - end_blk = (offset + length) >> blkbits; -if (written_blk < end_blk &&ext4_can_truncate (inode)) - truncate = true; - } -/* -* Remove inode from orphan list if we were extending a inode and -* everything went fine. -*/ -if (!truncate && inode->i_nlink && - !list_empty (&EXT4_I (inode)->i_orphan)) -ext4_orphan_del (handle, inode); -ext4_journal_stop (handle); -if (truncate) { -ext4_truncate_failed_write (inode); -orphan_del: -/* -* If truncate failed early the inode might still be on the -* orphan list; we need to make sure the inode is removed from -* the orphan list in that case. -*/ -if (inode->i_nlink) -ext4_orphan_del (NULL , inode); - } -return ret; +return 0 ; }const struct iomap_ops ext4_iomap_ops = {
Re: [PATCH v4 5/8] ext4: move inode extension/truncate code out from ->iomap_end() callback
Quoted 13 lines · Ritesh Harjani
Quoted 12 lines · Matthew Bobrowski
In preparation for implementing the iomap direct I/O write path modifications, the inode extension/truncate code needs to be moved out from
ext4_iomap_end(). For direct I/O, if the current code remained withinext4_iomap_end()it would behave incorrectly. Updating the inode size prior to converting unwritten extents to written extents will potentially allow a racing direct I/O read operation to find unwritten extents before they've been correctly converted.The inode extension/truncate code has been moved out into a new helper
ext4_handle_inode_extension(). This function has been designed so that it can be used by both DAX and direct I/O paths.
Quoted 5 lines
Quoted 1 line
Signed-off-by Matthew Bobrowski <[email protected]>checkpatch shows some whitespaces error in your comments in this patch.
But apart from that, patch looks good to me.
Yeah, I will fix those.
Quoted 3 lines
You may add:
Reviewed-by Ritesh Harjani <[email protected]>
Thanks!
--<M>--
PATCH v4 6/8 ext4: move inode extension checks out from ext4_iomap_alloc()
In reply to Matthew BobrowskiWe lift the inode extension/orphan list handling logic out from ext4_iomap_alloc() and place it within the caller ext4_dax_write_iter().
--- fs/ext4/file.c | 17 +++++++++++++++++ fs/ext4/inode.c | 22 ---------------------- 2 files changed, 17 insertions(+), 22 deletions(-)
fs/ext4/file.c +17 -0
@@ -309,6 +309,7 @@ ext4_dax_write_iter(struct kiocb *iocb, struct iov_iter *from)ssize_t ret;size_t count;loff_t offset; +handle_t *handle;struct inode *inode =file_inode (iocb->ki_filp);if (!inode_trylock (inode)) {
@@ -328,6 +329,22 @@ ext4_dax_write_iter(struct kiocb *iocb, struct iov_iter *from) offset = iocb->ki_pos; count =iov_iter_count (from); + +if (offset + count >EXT4_I (inode)->i_disksize) { + handle =ext4_journal_start (inode,EXT4_HT_INODE ,2 ); +if (IS_ERR (handle)) { + ret =PTR_ERR (handle); + goto out; + } + + ret =ext4_orphan_add (handle, inode); +if (ret) { +ext4_journal_stop (handle); + goto out; + } +ext4_journal_stop (handle); + } + ret =dax_iomap_rw (iocb, from, &ext4_iomap_ops); error =ext4_handle_inode_extension (inode, offset, ret, count);
fs/ext4/inode.c +0 -22
@@ -3508,7 +3508,6 @@ static int ext4_iomap_alloc(struct inode *inode, struct ext4_map_blocks *map) {handle_t *handle; -u8 blkbits = inode->i_blkbits;int ret, dio_credits, retries =0 ;/*
@@ -3530,28 +3529,7 @@ static int ext4_iomap_alloc(struct inode *inode,return PTR_ERR (handle); ret =ext4_map_blocks (handle, inode, map,EXT4_GET_BLOCKS_CREATE_ZERO ); -if (ret <0 ) - goto journal_stop; -/* -* If we have allocated blocks beyond the EOF, we need to make -* sure that they get truncate if we crash before updating the -* inode size metadata in ext4_iomap_end(). For faults, we -* don't need to do that (and cannot due to the orphan list -* operations needing an inode_lock()). If we happen to -* instantiate blocks beyond EOF, it is because we race with a -* truncate operation, which already has added the inode onto -* the orphan list. -*/ -if (!(flags &IOMAP_FAULT ) && first_block + map->m_len > - (i_size_read (inode) + (1 << blkbits) -1 ) >> blkbits) { -int err; - - err =ext4_orphan_add (handle, inode); -if (err <0 ) - ret = err; - } -journal_stop:ext4_journal_stop (handle);if (ret == -ENOSPC &&ext4_should_retry_alloc (inode->i_sb, &retries)) goto retry;
Signature · 1 line
2.20.1
Re: [PATCH v4 6/8] ext4: move inode extension checks out from ext4_iomap_alloc()
Quoted 5 lines · Matthew Bobrowski
We lift the inode extension/orphan list handling logic out from
ext4_iomap_alloc()and place it within the callerext4_dax_write_iter().Signed-off-by Matthew Bobrowski <[email protected]>
The patch looks good to me. You can add:
Honza
Quoted 84 lines
--- fs/ext4/file.c | 17 +++++++++++++++++ fs/ext4/inode.c | 22 ---------------------- 2 files changed, 17 insertions(+), 22 deletions(-)fs/ext4/file.c +17
-0@@ -309,6 +309,7 @@ ext4_dax_write_iter(struct kiocb *iocb, struct iov_iter *from)ssize_t ret;size_t count;loff_t offset; +handle_t *handle;struct inode *inode =file_inode (iocb->ki_filp);if (!inode_trylock (inode)) {@@ -328,6 +329,22 @@ ext4_dax_write_iter(struct kiocb *iocb, struct iov_iter *from) offset = iocb->ki_pos; count =iov_iter_count (from); + +if (offset + count >EXT4_I (inode)->i_disksize) { + handle =ext4_journal_start (inode,EXT4_HT_INODE ,2 ); +if (IS_ERR (handle)) { + ret =PTR_ERR (handle); + goto out; + } + + ret =ext4_orphan_add (handle, inode); +if (ret) { +ext4_journal_stop (handle); + goto out; + } +ext4_journal_stop (handle); + } + ret =dax_iomap_rw (iocb, from, &ext4_iomap_ops); error =ext4_handle_inode_extension (inode, offset, ret, count);fs/ext4/inode.c +0
-22@@ -3508,7 +3508,6 @@ static int ext4_iomap_alloc(struct inode *inode, struct ext4_map_blocks *map) {handle_t *handle; -u8 blkbits = inode->i_blkbits;int ret, dio_credits, retries =0 ;/* @@ -3530,28 +3529,7 @@ static int ext4_iomap_alloc(struct inode *inode,return PTR_ERR (handle); ret =ext4_map_blocks (handle, inode, map,EXT4_GET_BLOCKS_CREATE_ZERO ); -if (ret <0 ) - goto journal_stop; -/* -* If we have allocated blocks beyond the EOF, we need to make -* sure that they get truncate if we crash before updating the -* inode size metadata in ext4_iomap_end(). For faults, we -* don't need to do that (and cannot due to the orphan list -* operations needing an inode_lock()). If we happen to -* instantiate blocks beyond EOF, it is because we race with a -* truncate operation, which already has added the inode onto -* the orphan list. -*/ -if (!(flags &IOMAP_FAULT ) && first_block + map->m_len > - (i_size_read (inode) + (1 << blkbits) -1 ) >> blkbits) { -int err; - - err =ext4_orphan_add (handle, inode); -if (err <0 ) - ret = err; - } -journal_stop:ext4_journal_stop (handle);if (ret == -ENOSPC &&ext4_should_retry_alloc (inode->i_sb, &retries)) goto retry;Signature · 1 line
2.20.1
Signature · 2 lines
Jan Kara <[email protected]> SUSE Labs, CR
Re: [PATCH v4 6/8] ext4: move inode extension checks out from ext4_iomap_alloc()
Quoted 10 lines · Jan Kara
Quoted 5 lines · Matthew Bobrowski
We lift the inode extension/orphan list handling logic out from
ext4_iomap_alloc()and place it within the callerext4_dax_write_iter().Signed-off-by Matthew Bobrowski <[email protected]>The patch looks good to me. You can add:
Reviewed-by Jan Kara <[email protected]>
Thanks Jan! :)
--<M>--
Re: [PATCH v4 6/8] ext4: move inode extension checks out from ext4_iomap_alloc()
In reply to Matthew BobrowskiQuoted 5 lines · Matthew Bobrowski
We lift the inode extension/orphan list handling logic out from
ext4_iomap_alloc()and place it within the callerext4_dax_write_iter().Signed-off-by Matthew Bobrowski <[email protected]>
This looks good. Should solve our previous lengthy discussion about orphan handling :)
You may add:
Quoted 82 lines
--- fs/ext4/file.c | 17 +++++++++++++++++ fs/ext4/inode.c | 22 ---------------------- 2 files changed, 17 insertions(+), 22 deletions(-)fs/ext4/file.c +17
-0@@ -309,6 +309,7 @@ ext4_dax_write_iter(struct kiocb *iocb, struct iov_iter *from)ssize_t ret;size_t count;loff_t offset; +handle_t *handle;struct inode *inode =file_inode (iocb->ki_filp);if (!inode_trylock (inode)) {@@ -328,6 +329,22 @@ ext4_dax_write_iter(struct kiocb *iocb, struct iov_iter *from) offset = iocb->ki_pos; count =iov_iter_count (from); + +if (offset + count >EXT4_I (inode)->i_disksize) { + handle =ext4_journal_start (inode,EXT4_HT_INODE ,2 ); +if (IS_ERR (handle)) { + ret =PTR_ERR (handle); + goto out; + } + + ret =ext4_orphan_add (handle, inode); +if (ret) { +ext4_journal_stop (handle); + goto out; + } +ext4_journal_stop (handle); + } + ret =dax_iomap_rw (iocb, from, &ext4_iomap_ops); error =ext4_handle_inode_extension (inode, offset, ret, count);fs/ext4/inode.c +0
-22@@ -3508,7 +3508,6 @@ static int ext4_iomap_alloc(struct inode *inode, struct ext4_map_blocks *map) {handle_t *handle; -u8 blkbits = inode->i_blkbits;int ret, dio_credits, retries =0 ;/* @@ -3530,28 +3529,7 @@ static int ext4_iomap_alloc(struct inode *inode,return PTR_ERR (handle); ret =ext4_map_blocks (handle, inode, map,EXT4_GET_BLOCKS_CREATE_ZERO ); -if (ret <0 ) - goto journal_stop; -/* -* If we have allocated blocks beyond the EOF, we need to make -* sure that they get truncate if we crash before updating the -* inode size metadata in ext4_iomap_end(). For faults, we -* don't need to do that (and cannot due to the orphan list -* operations needing an inode_lock()). If we happen to -* instantiate blocks beyond EOF, it is because we race with a -* truncate operation, which already has added the inode onto -* the orphan list. -*/ -if (!(flags &IOMAP_FAULT ) && first_block + map->m_len > - (i_size_read (inode) + (1 << blkbits) -1 ) >> blkbits) { -int err; - - err =ext4_orphan_add (handle, inode); -if (err <0 ) - ret = err; - } -journal_stop:ext4_journal_stop (handle);if (ret == -ENOSPC &&ext4_should_retry_alloc (inode->i_sb, &retries)) goto retry;
Re: [PATCH v4 6/8] ext4: move inode extension checks out from ext4_iomap_alloc()
Quoted 3 lines · Ritesh Harjani
On 10/3/19 5:04 PM, Matthew Bobrowski wrote:
This looks good. Should solve our previous lengthy discussion about orphan handling :)
Yeah, although I'm still not the biggest fan of this approach.
Quoted 2 lines
You may add:
Reviewed-by Ritesh Harjani <[email protected]>
Thanks Ritesh!
--<M>--
PATCH v4 7/8 ext4: reorder map.m_flags checks in ext4_set_iomap()
In reply to Matthew BobrowskiFor iomap direct IO write code path changes, we need to accommodate for the case where the block mapping flags passed to ext4_map_blocks() will result in m_flags having both EXT4_MAP_MAPPED and EXT4_MAP_UNWRITTEN bits set. In order for the allocated unwritten extents to be converted properly in the end_io handler, iomap->type must be set to IOMAP_UNWRITTEN, so we need to reshuffle the conditional statement in order to achieve this.
This change is a no-op for DAX code path as the block mapping flag passed to ext4_map_blocks() when IS_DAX(inode) never results in EXT4_MAP_MAPPED and EXT4_MAP_UNWRITTEN being set at once.
--- fs/ext4/inode.c | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-)
fs/ext4/inode.c +13 -3
@@ -3420,10 +3420,20 @@ static int ext4_set_iomap(struct inode *inode, struct iomap *iomap, u16 type, iomap->type = type; iomap->addr =IOMAP_NULL_ADDR ; }else { -if (map->m_flags &EXT4_MAP_MAPPED ) { - iomap->type =IOMAP_MAPPED ; - }else if (map->m_flags &EXT4_MAP_UNWRITTEN ) { +/* +* Flags passed to ext4_map_blocks() for direct I/O +* writes can result in map->m_flags having both +* EXT4_MAP_MAPPED and EXT4_MAP_UNWRITTEN bits set. In +* order for allocated extents to be converted to +* written extents in the ->end_io handler correctly, +* we need to ensure that the iomap->type is set +* approprately. Thus, we need to check whether +* EXT4_MAP_UNWRITTEN is set first. +*/ +if (map->m_flags &EXT4_MAP_UNWRITTEN ) { iomap->type =IOMAP_UNWRITTEN ; + }else if (map->m_flags &EXT4_MAP_MAPPED ) { + iomap->type =IOMAP_MAPPED ; }else {WARN_ON_ONCE (1 );return -EIO ;
Signature · 1 line
2.20.1
Re: [PATCH v4 7/8] ext4: reorder map.m_flags checks in ext4_set_iomap()
Quoted 8 lines · Matthew Bobrowski
For iomap direct IO write code path changes, we need to accommodate for the case where the block mapping flags passed to
ext4_map_blocks()will result inm_flagshaving bothEXT4_MAP_MAPPEDandEXT4_MAP_UNWRITTENbits set. In order for the allocated unwritten extents to be converted properly in theend_iohandler,iomap->typemust be set toIOMAP_UNWRITTEN, so we need to reshuffle the conditional statement in order to achieve this.
Quoted 5 lines
This change is a no-op for DAX code path as the block mapping flag passed to
ext4_map_blocks()whenIS_DAX(inode)never results inEXT4_MAP_MAPPEDandEXT4_MAP_UNWRITTENbeing set at once.Signed-off-by Matthew Bobrowski <[email protected]>
The patch looks good to me. You can add:
Just those 72 columns limited comment lines... ;)
Honza
Quoted 35 lines
--- fs/ext4/inode.c | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-)fs/ext4/inode.c +13
-3@@ -3420,10 +3420,20 @@ static int ext4_set_iomap(struct inode *inode, struct iomap *iomap, u16 type, iomap->type = type; iomap->addr =IOMAP_NULL_ADDR ; }else { -if (map->m_flags &EXT4_MAP_MAPPED ) { - iomap->type =IOMAP_MAPPED ; - }else if (map->m_flags &EXT4_MAP_UNWRITTEN ) { +/* +* Flags passed to ext4_map_blocks() for direct I/O +* writes can result in map->m_flags having both +* EXT4_MAP_MAPPED and EXT4_MAP_UNWRITTEN bits set. In +* order for allocated extents to be converted to +* written extents in the ->end_io handler correctly, +* we need to ensure that the iomap->type is set +* approprately. Thus, we need to check whether +* EXT4_MAP_UNWRITTEN is set first. +*/ +if (map->m_flags &EXT4_MAP_UNWRITTEN ) { iomap->type =IOMAP_UNWRITTEN ; + }else if (map->m_flags &EXT4_MAP_MAPPED ) { + iomap->type =IOMAP_MAPPED ; }else {WARN_ON_ONCE (1 );return -EIO ;Signature · 1 line
2.20.1
Signature · 2 lines
Jan Kara <[email protected]> SUSE Labs, CR
Re: [PATCH v4 7/8] ext4: reorder map.m_flags checks in ext4_set_iomap()
Quoted 3 lines · Jan Kara
The patch looks good to me. You can add:
Reviewed-by Jan Kara <[email protected]>
Thanks Jan!
Quoted 1 line
Just those 72 columns limited comment lines... ;)
*nod* - will be fixed!
--<M>--
Re: [PATCH v4 7/8] ext4: reorder map.m_flags checks in ext4_set_iomap()
In reply to Matthew BobrowskiQuoted 8 lines · Matthew Bobrowski
For iomap direct IO write code path changes, we need to accommodate for the case where the block mapping flags passed to
ext4_map_blocks()will result inm_flagshaving bothEXT4_MAP_MAPPEDandEXT4_MAP_UNWRITTENbits set. In order for the allocated unwritten extents to be converted properly in theend_iohandler,iomap->typemust be set toIOMAP_UNWRITTEN, so we need to reshuffle the conditional statement in order to achieve this.
Quoted 5 lines
This change is a no-op for DAX code path as the block mapping flag passed to
ext4_map_blocks()whenIS_DAX(inode)never results inEXT4_MAP_MAPPEDandEXT4_MAP_UNWRITTENbeing set at once.Signed-off-by Matthew Bobrowski <[email protected]>
You may be changing the function parameters & name here, (in ext4_set_iomap)
But functionality wise the patch looks good to me.
You may add:
Quoted 33 lines
--- fs/ext4/inode.c | 16 +++++++++++++--- 1 file changed, 13 insertions(+), 3 deletions(-)fs/ext4/inode.c +13
-3@@ -3420,10 +3420,20 @@ static int ext4_set_iomap(struct inode *inode, struct iomap *iomap, u16 type, iomap->type = type; iomap->addr =IOMAP_NULL_ADDR ; }else { -if (map->m_flags &EXT4_MAP_MAPPED ) { - iomap->type =IOMAP_MAPPED ; - }else if (map->m_flags &EXT4_MAP_UNWRITTEN ) { +/* +* Flags passed to ext4_map_blocks() for direct I/O +* writes can result in map->m_flags having both +* EXT4_MAP_MAPPED and EXT4_MAP_UNWRITTEN bits set. In +* order for allocated extents to be converted to +* written extents in the ->end_io handler correctly, +* we need to ensure that the iomap->type is set +* approprately. Thus, we need to check whether +* EXT4_MAP_UNWRITTEN is set first. +*/ +if (map->m_flags &EXT4_MAP_UNWRITTEN ) { iomap->type =IOMAP_UNWRITTEN ; + }else if (map->m_flags &EXT4_MAP_MAPPED ) { + iomap->type =IOMAP_MAPPED ; }else {WARN_ON_ONCE (1 );return -EIO ;
Re: [PATCH v4 7/8] ext4: reorder map.m_flags checks in ext4_set_iomap()
Quoted 2 lines · Ritesh Harjani
You may be changing the function parameters & name here, (in
ext4_set_iomap)
Hm, maybe. :P It all depends on the outcome of what we discuss in 1/8.
Quoted 4 lines
But functionality wise the patch looks good to me.
You may add:
Reviewed-by Ritesh Harjani <[email protected]>
Great, thanks Ritesh!
--<M>--
PATCH v4 8/8 ext4: introduce direct I/O write path using iomap infrastructure
In reply to Matthew BobrowskiThis patch introduces a new direct I/O write code path implementation that makes use of the iomap infrastructure.
All direct I/O write operations are now passed from the ->write_iter() callback to the new function ext4_dio_write_iter(). This function is responsible for calling into iomap infrastructure via iomap_dio_rw(). Snippets of the direct I/O code from within ext4_file_write_iter(), such as checking whether the IO request is unaligned asynchronous I/O, or whether it will ber overwriting allocated and initialized blocks has been moved out and into ext4_dio_write_iter().
The block mapping flags that are passed to ext4_map_blocks() from within ext4_dio_get_block() and friends have effectively been taken out and introduced within the ext4_iomap_alloc().
For inode extension cases, the ->end_io() callback ext4_dio_write_end_io() is responsible for calling into ext4_handle_inode_extension() and performing the necessary metadata updates. Failed writes that we're intended to be extend the inode will have blocks truncated accordingly. The ->end_io() handler is also responsible for converting allocated unwritten extents to written extents.
In the instance of a short write, we fallback to buffered I/O and use that method to complete whatever is left over in 'iter'. Any blocks that have been allocated in preparation for direct I/O write will be reused by buffered I/O, so there's no issue with leaving allocated blocks beyond EOF.
Existing direct I/O write buffer_head code has been removed as it's now redundant.
--- fs/ext4/ext4.h | 3 - fs/ext4/extents.c | 11 +- fs/ext4/file.c | 245 ++++++++++++++++++--------- fs/ext4/inode.c | 411 +++++----------------------------------------- 4 files changed, 214 insertions(+), 456 deletions(-)
fs/ext4/ext4.h +0 -3
@@ -1579,7 +1579,6 @@ enum {EXT4_STATE_NO_EXPAND ,/* No space for expansion */ EXT4_STATE_DA_ALLOC_CLOSE ,/* Alloc DA blks on close */ EXT4_STATE_EXT_MIGRATE ,/* Inode is migrating */ -EXT4_STATE_DIO_UNWRITTEN ,/* need convert on dio done*/ EXT4_STATE_NEWENTRY ,/* File just added to dir */ EXT4_STATE_MAY_INLINE_DATA ,/* may have in-inode data */ EXT4_STATE_EXT_PRECACHED, /* extents have been precached */
@@ -2560,8 +2559,6 @@ int ext4_get_block_unwritten(struct inode *inode, sector_t iblock, struct buffer_head *bh_result, int create);int ext4_get_block (struct inode *inode,sector_t iblock,struct buffer_head *bh_result,int create); -int ext4_dio_get_block (struct inode *inode,sector_t iblock, -struct buffer_head *bh_result,int create);int ext4_da_get_block_prep (struct inode *inode,sector_t iblock,struct buffer_head *bh,int create); int ext4_walk_page_buffers(handle_t *handle,
fs/ext4/extents.c +2 -9
@@ -1753,16 +1753,9 @@ ext4_can_extents_be_merged(struct inode *inode, struct ext4_extent *ex1,*/ if (ext1_ee_len + ext2_ee_len >EXT_INIT_MAX_LEN )return 0 ; -/* -* The check for IO to unwritten extent is somewhat racy as we -* increment i_unwritten / set EXT4_STATE_DIO_UNWRITTEN only after -* dropping i_data_sem. But reserved blocks should save us in that -* case. -*/ +if (ext4_ext_is_unwritten (ex1) && - (ext4_test_inode_state (inode,EXT4_STATE_DIO_UNWRITTEN ) || -atomic_read (&EXT4_I (inode)->i_unwritten) || - (ext1_ee_len + ext2_ee_len >EXT_UNWRITTEN_MAX_LEN ))) + ext1_ee_len + ext2_ee_len >EXT_UNWRITTEN_MAX_LEN )return 0 ;#ifdef AGGRESSIVE_TEST if (ext1_ee_len >=4 )
fs/ext4/file.c +170 -75
331 lines not on this page · raw message
fs/ext4/inode.c +42 -369
459 lines not on this page · raw message
Signature · 1 line
2.20.1
Jan Kara
reviewerRe: [PATCH v4 8/8] ext4: introduce direct I/O write path using iomap infrastructure
Quoted 24 lines · Matthew Bobrowski
This patch introduces a new direct I/O write code path implementation that makes use of the iomap infrastructure.
All direct I/O write operations are now passed from the ->write_iter() callback to the new function
ext4_dio_write_iter(). This function is responsible for calling into iomap infrastructure viaiomap_dio_rw(). Snippets of the direct I/O code from withinext4_file_write_iter(), such as checking whether the IO request is unaligned asynchronous I/O, or whether it will ber overwriting allocated and initialized blocks has been moved out and intoext4_dio_write_iter().The block mapping flags that are passed to
ext4_map_blocks()from withinext4_dio_get_block()and friends have effectively been taken out and introduced within theext4_iomap_alloc().For inode extension cases, the ->end_io() callback
ext4_dio_write_end_io()is responsible for calling intoext4_handle_inode_extension()and performing the necessary metadata updates. Failed writes that we're intended to be extend the inode will have blocks truncated accordingly. The ->end_io() handler is also responsible for converting allocated unwritten extents to written extents.
Quoted 7 lines
In the instance of a short write, we fallback to buffered I/O and use that method to complete whatever is left over in 'iter'.
Any blocks
that have been allocated in preparation for direct I/O write will be reused by buffered I/O, so there's no issue with leaving allocated blocks beyond EOF.
This actually is not true as ext4_truncate_failed_write() will trim blocks beyond EOF. Also this would not be 100% reliable as if we crash between DIO short write succeeding and buffered write happening, we would leave inode with blocks beyond EOF. So I'd just remove this sentence.
Quoted 4 lines
Existing direct I/O write
buffer_headcode has been removed as it's now redundant.Signed-off-by Matthew Bobrowski <[email protected]>
...
Review
Quoted 12 lines
(quoted diff) +12
-0+static int ext4_dio_write_end_io(struct kiocb *iocb, ssize_t size, + int error, unsigned int flags) +{ + loff_t offset = iocb->ki_pos; + struct inode *inode = file_inode(iocb->ki_filp); + + if (!error && (flags & IOMAP_DIO_UNWRITTEN)) + error = ext4_convert_unwritten_extents(NULL, inode, offset, + size); + return ext4_handle_inode_extension(inode, offset, error ? : size, + size); +}
I was pondering about this and I don't think we have it quite correct. Still :-|. The problem is that iomap_dio_complete() will pass dio->size as 'size', which is the amount of submitted IO but not necessarily the amount of blocks that were mapped (that can be larger). Thus ext4_handle_inode_extension() can miss the fact that there are blocks beyond EOF that need to be trimmed. And we have no way of finding that out inside our ->end_io handler. Even iomap_dio_complete() doesn't have that information so we'd need to add 'original length' to struct iomap_dio and then pass it do ->end_io.
Seeing how difficult it is when a filesystem wants to complete the iocb synchronously (regardless whether it is async or sync) and have all the information in one place for further processing, I think it would be the easiest to provide iomap_dio_rw_wait() that forces waiting for the iocb to complete *and* returns the appropriate return value instead of pretty useless EIOCBQUEUED. It is actually pretty trivial (patch attached). With this we can then just call iomap_dio_rw_sync() for the inode extension case with ->end_io doing just the unwritten extent processing and then call ext4_handle_inode_extension() from ext4_direct_write_iter() where we would have all the information we need.
Christoph, Darrick, what do you think about extending iomap like in the attached patch (plus sample use in XFS)?
Honza
Signature · 2 lines
Jan Kara <[email protected]> SUSE Labs, CR
From 240d0f2c96d81d9ef68c640b53f0b987d9e0333e Mon Sep 17 00:00:00 2001
From: Jan Kara <[email protected]>
Date: Tue, 8 Oct 2019 15:57:11 +0200
Subject: [PATCH 1/2] iomap: Allow forcing of waiting for running DIO in
iomap_dio_rw()
Filesystems do not support doing IO and asynchronous in some cases. For example in case of unaligned writes or in case file size needs to be extended (e.g. for ext4). Instead of forcing filesystem to wait for AIO in such cases, provide iomap_dio_rw_wait() which does the waiting for IO and also executes iomap_dio_complete() inline providing its return value to the caller.
--- fs/iomap/direct-io.c | 8 ++++---- include/linux/iomap.h | 16 ++++++++++++++-- 2 files changed, 18 insertions(+), 6 deletions(-)
fs/iomap/direct-io.c +4 -4
@@ -391,8 +391,9 @@ iomap_dio_actor(struct inode *inode, loff_t pos, loff_t length,* completion. */ ssize_t -iomap_dio_rw (struct kiocb *iocb,struct iov_iter *iter, -const struct iomap_ops *ops,const struct iomap_dio_ops *dops) +__iomap_dio_rw (struct kiocb *iocb,struct iov_iter *iter, +const struct iomap_ops *ops,const struct iomap_dio_ops *dops, +bool wait_for_completion) {struct address_space *mapping = iocb->ki_filp->f_mapping;struct inode *inode =file_inode (iocb->ki_filp);
@@ -400,7 +401,6 @@ iomap_dio_rw(struct kiocb *iocb, struct iov_iter *iter,loff_t pos = iocb->ki_pos, start = pos;loff_t end = iocb->ki_pos + count -1 , ret =0 ;unsigned int flags =IOMAP_DIRECT ; -bool wait_for_completion =is_sync_kiocb (iocb);struct blk_plug plug;struct iomap_dio *dio;
@@ -555,4 +555,4 @@ iomap_dio_rw(struct kiocb *iocb, struct iov_iter *iter,kfree (dio);return ret; } -EXPORT_SYMBOL_GPL (iomap_dio_rw); +EXPORT_SYMBOL_GPL (__iomap_dio_rw);
include/linux/iomap.h +14 -2
@@ -194,8 +194,20 @@ struct iomap_dio_ops { unsigned flags); }; -ssize_t iomap_dio_rw (struct kiocb *iocb,struct iov_iter *iter, -const struct iomap_ops *ops,const struct iomap_dio_ops *dops); +ssize_t __iomap_dio_rw (struct kiocb *iocb,struct iov_iter *iter, +const struct iomap_ops *ops,const struct iomap_dio_ops *dops, +bool wait_for_completion); +static inline ssize_t iomap_dio_rw (struct kiocb *iocb,struct iov_iter *iter, +const struct iomap_ops *ops,const struct iomap_dio_ops *dops) +{ +return __iomap_dio_rw (iocb, iter, ops, dops,is_sync_kiocb (iocb)); +} +static inline ssize_t iomap_dio_rw_wait (struct kiocb *iocb, +struct iov_iter *iter,const struct iomap_ops *ops, +const struct iomap_dio_ops *dops) +{ +return __iomap_dio_rw (iocb, iter, ops, dops, true); +}int iomap_dio_iopoll (struct kiocb *kiocb,bool spin);#ifdef CONFIG_SWAP
Signature · 1 line
2.16.4
From 26163692c3e01f5c51e895197e4f7ae0b674ae5d Mon Sep 17 00:00:00 2001
From: Jan Kara <[email protected]>
Date: Tue, 8 Oct 2019 16:35:41 +0200
Subject: [PATCH 2/2] xfs: Use iomap_dio_rw_wait()
Use iomap_dio_rw_wait() instead of opencoding the wait.
--- fs/xfs/xfs_file.c | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-)
fs/xfs/xfs_file.c +9 -7
@@ -547,15 +547,17 @@ xfs_file_dio_aio_write( }trace_xfs_file_direct_write (ip, count, iocb->ki_pos); - ret =iomap_dio_rw (iocb, from, &xfs_iomap_ops, &xfs_dio_write_ops); -/* -* If unaligned, this is the only IO in-flight. If it has not yet -* completed, wait on it before we release the iolock to prevent -* subsequent overlapping IO. +* If unaligned, this is the only IO in-flight. Wait on it before we +* release the iolock to prevent subsequent overlapping IO. */ -if (ret == -EIOCBQUEUED && unaligned_io) -inode_dio_wait (inode); +if (unaligned_io) { + ret =iomap_dio_rw_wait (iocb, from, &xfs_iomap_ops, + &xfs_dio_write_ops); + }else { + ret =iomap_dio_rw (iocb, from, &xfs_iomap_ops, + &xfs_dio_write_ops); + } out:xfs_iunlock (ip, iolock);
Signature · 1 line
2.16.4
Re: [PATCH v4 8/8] ext4: introduce direct I/O write path using iomap infrastructure
Quoted 11 lines · Jan Kara
Seeing how difficult it is when a filesystem wants to complete the iocb synchronously (regardless whether it is async or sync) and have all the information in one place for further processing, I think it would be the easiest to provide
iomap_dio_rw_wait()that forces waiting for the iocb to complete *and* returns the appropriate return value instead of pretty useless EIOCBQUEUED. It is actually pretty trivial (patch attached). With this we can then just calliomap_dio_rw_sync()for the inode extension case with ->end_io doing just the unwritten extent processing and then callext4_handle_inode_extension()fromext4_direct_write_iter()where we would have all the information we need.
Quoted 2 lines
Christoph, Darrick, what do you think about extending iomap like in the attached patch (plus sample use in XFS)?
I vaguely remember suggesting something like this but Brian or Dave convinced me it wasn't a good idea. This will require a trip to the xfs or fsdevel archives from when the inode_dio_wait was added in XFS.
But if we decide it actully works this time around please don't add the __ variant but just add the parameter to iomap_dio_rw directly.
Jan Kara
reviewerRe: [PATCH v4 8/8] ext4: introduce direct I/O write path using iomap infrastructure
Quoted 12 lines · Christoph Hellwig
Quoted 11 lines · Jan Kara
Seeing how difficult it is when a filesystem wants to complete the iocb synchronously (regardless whether it is async or sync) and have all the information in one place for further processing, I think it would be the easiest to provide
iomap_dio_rw_wait()that forces waiting for the iocb to complete *and* returns the appropriate return value instead of pretty useless EIOCBQUEUED. It is actually pretty trivial (patch attached). With this we can then just calliomap_dio_rw_sync()for the inode extension case with ->end_io doing just the unwritten extent processing and then callext4_handle_inode_extension()fromext4_direct_write_iter()where we would have all the information we need.
Quoted 6 lines
Quoted 2 lines
Christoph, Darrick, what do you think about extending iomap like in the attached patch (plus sample use in XFS)?
I vaguely remember suggesting something like this but Brian or Dave convinced me it wasn't a good idea. This will require a trip to the xfs or fsdevel archives from when the
inode_dio_waitwas added in XFS.
I think you refer to this [1] message from Brian:
It's not quite that simple..
FWIW, the discussion (between Dave and I) for how best to solve this started offline prior to sending the patch and pretty much started with the idea of changing the async I/O to sync as you suggest here. I backed off from that because it's too subtle given the semantics between the higher level aio code and lower level dio code for async I/O. By that I mean either can be responsible for calling the ->ki_complete() callback in the iocb on I/O completion.
IOW, if we receive an async direct I/O, clear ->ki_complete() as you describe above and submit it, the dio code will wait on I/O and return the size of the I/O on successful completion. It will not have called ->ki_complete(), however. Rather, the >0 return value indicates that aio_rw_done() must call ->ki_complete() after xfs_file_write_iter() returns, but we would have already cleared the function pointer.
I think it is technically possible to use this technique by clearing and restoring ->ki_complete(), but in general we've visited this "change the I/O type" approach twice now and we've (collectively) got it wrong both times (the first error in thinking was that XFS would need to call ->ki_complete()). IMO, this demonstrates that it's not worth the complexity to insert ourselves into this dependency chain when we can accomplish the same thing with a simple dio wait call.
---
Which is fair enough. I've been looking at the same and arrived at similar conclusion ;) (BTW, funnily enough ocfs2 seems to do this dance with clearing and restoring ki_complete). But what I propose is something different - just wait for IO in iomap_dio_rw() which avoids the need to clear & restore ->ki_complete() while at the same time while providing fully-sync IO experience to the caller. So Brians objection doesn't apply here.
Quoted 2 lines
But if we decide it actully works this time around please don't add the __ variant but just add the parameter to
iomap_dio_rwdirectly.
Yeah, I was undecided on this one as well. Will change this and post the patches to fsdevel & xfs lists.
Honza
[1] https://lore.kernel.org/linux-xfs/20190325135124.GD52167@bfoster/
Signature · 2 lines
Jan Kara <[email protected]> SUSE Labs, CR
Re: [PATCH v4 8/8] ext4: introduce direct I/O write path using iomap infrastructure
In reply to Jan KaraQuoted 10 lines · Jan Kara
Quoted 4 lines · Matthew Bobrowski
Any blocks
that have been allocated in preparation for direct I/O write will be reused by buffered I/O, so there's no issue with leaving allocated blocks beyond EOF.This actually is not true as
ext4_truncate_failed_write()will trim blocks beyond EOF. Also this would not be 100% reliable as if we crash between DIO short write succeeding and buffered write happening, we would leave inode with blocks beyond EOF. So I'd just remove this sentence.
OK.
Quoted 19 lines
Quoted 4 lines
Existing direct I/O write
buffer_headcode has been removed as it's now redundant.Signed-off-by Matthew Bobrowski <[email protected]>...
Review
Quoted 12 lines
(quoted diff) +12
-0+static int ext4_dio_write_end_io(struct kiocb *iocb, ssize_t size, + int error, unsigned int flags) +{ + loff_t offset = iocb->ki_pos; + struct inode *inode = file_inode(iocb->ki_filp); + + if (!error && (flags & IOMAP_DIO_UNWRITTEN)) + error = ext4_convert_unwritten_extents(NULL, inode, offset, + size); + return ext4_handle_inode_extension(inode, offset, error ? : size, + size); +}I was pondering about this and I don't think we have it quite correct.
Quoted 8 lines
Still :-|. The problem is that
iomap_dio_complete()will passdio->sizeas 'size', which is the amount of submitted IO but not necessarily the amount of blocks that were mapped (that can be larger). Thusext4_handle_inode_extension()can miss the fact that there are blocks beyond EOF that need to be trimmed. And we have no way of finding that out inside our ->end_io handler. Eveniomap_dio_complete()doesn't have that information so we'd need to add 'original length' to structiomap_dioand then pass it do ->end_io.
Yes, I remember having a discussion around this in the past. The answer to this problem at the time was that any blocks that may have been allocated in preparation for the direct I/O write and we're not used would in fact be reused when we fell back to buffered I/O. The case that you're describing above, based on my understanding, would have to be a result of short write?
Quoted 10 lines
Seeing how difficult it is when a filesystem wants to complete the iocb synchronously (regardless whether it is async or sync) and have all the information in one place for further processing, I think it would be the easiest to provide
iomap_dio_rw_wait()that forces waiting for the iocb to complete *and* returns the appropriate return value instead of pretty useless EIOCBQUEUED. It is actually pretty trivial (patch attached). With this we can then just calliomap_dio_rw_sync()for the inode extension case with ->end_io doing just the unwritten extent processing and then callext4_handle_inode_extension()fromext4_direct_write_iter()where we would have all the information we need.
This could also work, nicely. But, if this isn't an option for whatever reason then we could go with what you suggested above? After all, I think it would make sense to pass such information about the write all the way through to the end, especially the ->end_io handler, seeing as though that's we're clean up should be performed in the instance of a failure, or a short write.
However, note that:
a) likely(my understanding may be wrong)
b) Someone a lot smarter than I has probably already thought this through and there's a real good reason why we don't cram such information about the write within the iomap structures and have them passed all the way through to the end...
:)
--<M>--