ext4: improve commit path performance for fast commit
Subsystems (2)
v3 cover ext4: improve commit path performance for fast commit
ext4: improve commit path performance for fast commit
This patch series supersedes the patch "ext4: remove journal barrier during fast commit" sent in Feb 2022.
This patch series reworks the fast commit's commit path to improve overall performance of the commit path. Following optimizations have been added in this series:
* Avoid having to lock the journal throughout the fast commit.
* Remove tracking of open handles per inode.
With the changes introduced in this patch series, now the commit path for fast commits is as follows:
[1] Lock the journal by calling jbd2_journal_lock_updates. This ensures that all the exsiting handles finish and no new handles can start.
[2] Mark all the fast commit eligible inodes as undergoing fast commit by setting "EXT4_STATE_FC_COMMITTING" state.
[3] Unlock the journal by calling jbd2_journal_unlock_updates. This allows starting of new handles. If new handles try to start an update on any of the inodes that are being committed, ext4_fc_track_inode() will block until those inodes have finished the fast commit.
[4] Submit data buffers of all the committing inodes.
[5] Wait for [4] to complete.
[6] Commit all the directory entry updates in the fast commit space.
[7] Commit all the changed inodes in the fast commit space and clear "EXT4_STATE_FC_COMMITTING" for all the inodes.
[8] Write tail tag to ensure atomicity of commits.
(The above flow has been documented in the code as well)
Instead of calling ext4_fc_track_inode() in ext4_journal_start() as I originally proposed on the code review of [PATCH V2 2/5] "ext4: ext4:
for committing inode, make ext4_fc_track_inode wait" [1], in this version I changed the behavior of ext4_reserve_inode_write() to also call ext4_fc_track_inode(). Let's call this approach 1.
I also evaluated another approach (approach 2) where ext4_reserve_inode_write() acts just as an assertion to ensure that inode is on fast commit list and the actual call to ext4_fc_track_inode() is done by ext4_journal_start(). However, this results in too many stray ext4_fc_track_inode() calls. Approach 1 reduces the number of stray ext4_fc_track_inode() calls and thus makes the code more maintainable.
However, approach 1 results in a potential deadlock where the caller can hang if they grab i_data_sem before calling ext4_fc_track_inode(). To handle that, I have added explicit calls to ext4_fc_track_inode() in such places. Eventually, when we migrate to using extent status tree for logical to physical mapping lookup, we can get rid of this ordering requirement and also remove these calls to ext4_fc_track_inode(). But, even after adding these stray calls, the number of stray calls to ext4_fc_track_inode() were less in approach 1 than in approach 2.
I verified that the patch series introduces no regressions in "quick" and "log" groups when "fast_commit" feature is enabled.
[1] https://www.spinics.net/lists/linux-ext4/msg82019.html
Harshad Shirwadkar (6):
ext4: convert i_fc_lock to spinlock
ext4: for committing inode, make ext4_fc_track_inode wait
ext4: mark inode dirty before grabbing i_data_sem in ext4_setattr
ext4: rework fast commit commit path
ext4: drop i_fc_updates from inode fc info
ext4: update code documentation
fs/ext4/ext4.h | 12 +-- fs/ext4/fast_commit.c | 240 +++++++++++++++++++++--------------------- fs/ext4/inline.c | 3 + fs/ext4/inode.c | 10 +- fs/ext4/super.c | 2 +- fs/jbd2/journal.c | 2 - 6 files changed, 136 insertions(+), 133 deletions(-)
Signature · 1 line
2.36.0.rc0.470.gd361397f0d-goog
PATCH v3 1/6 ext4: convert i_fc_lock to spinlock
From: Harshad Shirwadkar <[email protected]>
Convert ext4_inode_info->i_fc_lock to spinlock to avoid sleeping in invalid contexts.
--- fs/ext4/ext4.h | 7 +++++-- fs/ext4/fast_commit.c | 22 ++++++++++------------ fs/ext4/super.c | 2 +- 3 files changed, 16 insertions(+), 15 deletions(-)
fs/ext4/ext4.h +5 -2
@@ -1065,8 +1065,11 @@ struct ext4_inode_info {/* Fast commit wait queue for this inode */ wait_queue_head_t i_fc_wait; -/* Protect concurrent accesses on i_fc_lblk_start, i_fc_lblk_len */ -struct mutex i_fc_lock; +/* +* Protect concurrent accesses on i_fc_lblk_start, i_fc_lblk_len +* and inode's EXT4_FC_STATE_COMMITTING state bit. +*/ +spinlock_t i_fc_lock;/* * i_disksize keeps track of what the inode size is ON DISK, not
fs/ext4/fast_commit.c +10 -12
@@ -380,7 +380,7 @@ static int ext4_fc_track_template(int ret; tid = handle->h_transaction->t_tid; -mutex_lock (&ei->i_fc_lock); +spin_lock (&ei->i_fc_lock);if (tid == ei->i_sync_tid) { update = true; }else {
@@ -388,7 +388,7 @@ static int ext4_fc_track_template( ei->i_sync_tid = tid; } ret =__fc_track_fn (inode, args, update); -mutex_unlock (&ei->i_fc_lock); +spin_unlock (&ei->i_fc_lock);if (!enqueue)return ret;
@@ -420,11 +420,11 @@ static int __track_dentry_update(struct inode *inode, void *arg, bool update)struct dentry *dentry = dentry_update->dentry;struct ext4_sb_info *sbi =EXT4_SB (inode->i_sb); -mutex_unlock (&ei->i_fc_lock); +spin_unlock (&ei->i_fc_lock); node =kmem_cache_alloc (ext4_fc_dentry_cachep,GFP_NOFS );if (!node) {ext4_fc_mark_ineligible (inode->i_sb,EXT4_FC_REASON_NOMEM ,NULL ); -mutex_lock (&ei->i_fc_lock); +spin_lock (&ei->i_fc_lock);return -ENOMEM ; }
@@ -437,7 +437,7 @@ static int __track_dentry_update(struct inode *inode, void *arg, bool update)kmem_cache_free (ext4_fc_dentry_cachep, node);ext4_fc_mark_ineligible (inode->i_sb,EXT4_FC_REASON_NOMEM ,NULL ); -mutex_lock (&ei->i_fc_lock); +spin_lock (&ei->i_fc_lock);return -ENOMEM ; } memcpy((u8 *)node->fcd_name.name, dentry->d_name.name,
@@ -471,7 +471,7 @@ static int __track_dentry_update(struct inode *inode, void *arg, bool update)list_add_tail (&node->fcd_dilist, &ei->i_fc_dilist); }spin_unlock (&sbi->s_fc_lock); -mutex_lock (&ei->i_fc_lock); +spin_lock (&ei->i_fc_lock);return 0 ; }
@@ -611,10 +611,8 @@ static int __track_range(struct inode *inode, void *arg, bool update)struct __track_range_args *__arg = (struct __track_range_args *)arg; -if (inode->i_ino <EXT4_FIRST_INO (inode->i_sb)) { -ext4_debug ("Special inode %ld being modified\n" , inode->i_ino); +if (inode->i_ino <EXT4_FIRST_INO (inode->i_sb))return -ECANCELED ; - } oldstart = ei->i_fc_lblk_start;
@@ -906,15 +904,15 @@ static int ext4_fc_write_inode_data(struct inode *inode, u32 *crc)struct ext4_extent *ex;int ret; -mutex_lock (&ei->i_fc_lock); +spin_lock (&ei->i_fc_lock);if (ei->i_fc_lblk_len ==0 ) { -mutex_unlock (&ei->i_fc_lock); +spin_unlock (&ei->i_fc_lock);return 0 ; } old_blk_size = ei->i_fc_lblk_start; new_blk_size = ei->i_fc_lblk_start + ei->i_fc_lblk_len -1 ; ei->i_fc_lblk_len =0 ; -mutex_unlock (&ei->i_fc_lock); +spin_unlock (&ei->i_fc_lock); cur_lblk_off = old_blk_size; jbd_debug(1, "%s: will try writing %d to %d for inode %ld\n",
fs/ext4/super.c +1 -1
@@ -1347,7 +1347,7 @@ static struct inode *ext4_alloc_inode(struct super_block *sb)atomic_set (&ei->i_unwritten,0 );INIT_WORK (&ei->i_rsv_conversion_work, ext4_end_io_rsv_work);ext4_fc_init_inode (&ei->vfs_inode); -mutex_init (&ei->i_fc_lock); +spin_lock_init (&ei->i_fc_lock);return &ei->vfs_inode; }
Signature · 1 line
2.36.0.rc0.470.gd361397f0d-goog
Re: [PATCH v3 1/6] ext4: convert i_fc_lock to spinlock
Quoted 6 lines · Harshad Shirwadkar
From: Harshad Shirwadkar <[email protected]>
Convert
ext4_inode_info->i_fc_lockto spinlock to avoid sleeping in invalid contexts.Signed-off-by Harshad Shirwadkar <[email protected]>
Looks good. Feel free to add:
Honza
Quoted 125 lines
--- fs/ext4/ext4.h | 7 +++++-- fs/ext4/fast_commit.c | 22 ++++++++++------------ fs/ext4/super.c | 2 +- 3 files changed, 16 insertions(+), 15 deletions(-)fs/ext4/ext4.h +5
-2@@ -1065,8 +1065,11 @@ struct ext4_inode_info {/* Fast commit wait queue for this inode */ wait_queue_head_t i_fc_wait; -/* Protect concurrent accesses on i_fc_lblk_start, i_fc_lblk_len */ -struct mutex i_fc_lock; +/* +* Protect concurrent accesses on i_fc_lblk_start, i_fc_lblk_len +* and inode's EXT4_FC_STATE_COMMITTING state bit. +*/ +spinlock_t i_fc_lock;/* * i_disksize keeps track of what the inode size is ON DISK, not fs/ext4/fast_commit.c +10
-12@@ -380,7 +380,7 @@ static int ext4_fc_track_template(int ret; tid = handle->h_transaction->t_tid; -mutex_lock (&ei->i_fc_lock); +spin_lock (&ei->i_fc_lock);if (tid == ei->i_sync_tid) { update = true; }else {@@ -388,7 +388,7 @@ static int ext4_fc_track_template( ei->i_sync_tid = tid; } ret =__fc_track_fn (inode, args, update); -mutex_unlock (&ei->i_fc_lock); +spin_unlock (&ei->i_fc_lock);if (!enqueue)return ret;@@ -420,11 +420,11 @@ static int __track_dentry_update(struct inode *inode, void *arg, bool update)struct dentry *dentry = dentry_update->dentry;struct ext4_sb_info *sbi =EXT4_SB (inode->i_sb); -mutex_unlock (&ei->i_fc_lock); +spin_unlock (&ei->i_fc_lock); node =kmem_cache_alloc (ext4_fc_dentry_cachep,GFP_NOFS );if (!node) {ext4_fc_mark_ineligible (inode->i_sb,EXT4_FC_REASON_NOMEM ,NULL ); -mutex_lock (&ei->i_fc_lock); +spin_lock (&ei->i_fc_lock);return -ENOMEM ; }@@ -437,7 +437,7 @@ static int __track_dentry_update(struct inode *inode, void *arg, bool update)kmem_cache_free (ext4_fc_dentry_cachep, node);ext4_fc_mark_ineligible (inode->i_sb,EXT4_FC_REASON_NOMEM ,NULL ); -mutex_lock (&ei->i_fc_lock); +spin_lock (&ei->i_fc_lock);return -ENOMEM ; } memcpy((u8 *)node->fcd_name.name, dentry->d_name.name,@@ -471,7 +471,7 @@ static int __track_dentry_update(struct inode *inode, void *arg, bool update)list_add_tail (&node->fcd_dilist, &ei->i_fc_dilist); }spin_unlock (&sbi->s_fc_lock); -mutex_lock (&ei->i_fc_lock); +spin_lock (&ei->i_fc_lock);return 0 ; }@@ -611,10 +611,8 @@ static int __track_range(struct inode *inode, void *arg, bool update)struct __track_range_args *__arg = (struct __track_range_args *)arg; -if (inode->i_ino <EXT4_FIRST_INO (inode->i_sb)) { -ext4_debug ("Special inode %ld being modified\n" , inode->i_ino); +if (inode->i_ino <EXT4_FIRST_INO (inode->i_sb))return -ECANCELED ; - } oldstart = ei->i_fc_lblk_start;@@ -906,15 +904,15 @@ static int ext4_fc_write_inode_data(struct inode *inode, u32 *crc)struct ext4_extent *ex;int ret; -mutex_lock (&ei->i_fc_lock); +spin_lock (&ei->i_fc_lock);if (ei->i_fc_lblk_len ==0 ) { -mutex_unlock (&ei->i_fc_lock); +spin_unlock (&ei->i_fc_lock);return 0 ; } old_blk_size = ei->i_fc_lblk_start; new_blk_size = ei->i_fc_lblk_start + ei->i_fc_lblk_len -1 ; ei->i_fc_lblk_len =0 ; -mutex_unlock (&ei->i_fc_lock); +spin_unlock (&ei->i_fc_lock); cur_lblk_off = old_blk_size; jbd_debug(1, "%s: will try writing %d to %d for inode %ld\n",fs/ext4/super.c +1
-1@@ -1347,7 +1347,7 @@ static struct inode *ext4_alloc_inode(struct super_block *sb)atomic_set (&ei->i_unwritten,0 );INIT_WORK (&ei->i_rsv_conversion_work, ext4_end_io_rsv_work);ext4_fc_init_inode (&ei->vfs_inode); -mutex_init (&ei->i_fc_lock); +spin_lock_init (&ei->i_fc_lock);return &ei->vfs_inode; }Signature · 1 line
2.36.0.rc0.470.gd361397f0d-goog
Signature · 2 lines
Jan Kara <[email protected]> SUSE Labs, CR
PATCH v3 2/6 ext4: for committing inode, make ext4_fc_track_inode wait
In reply to Harshad ShirwadkarFrom: Harshad Shirwadkar <[email protected]>
If the inode that's being requested to track using ext4_fc_track_inode is being committed, then wait until the inode finishes the commit. Also, add calls to ext4_fc_track_inode at the right places.
With this patch, now calling ext4_reserve_inode_write() results in inode being tracked for next fast commit. A subtle lock ordering requirement with i_data_sem (which is documented in the code) requires that ext4_fc_track_inode() be called before grabbing i_data_sem. So, this patch also adds explicit ext4_fc_track_inode() calls in places where i_data_sem grabbed.
--- fs/ext4/fast_commit.c | 38 ++++++++++++++++++++++++++++++++++++++ fs/ext4/inline.c | 3 +++ fs/ext4/inode.c | 5 ++++- 3 files changed, 45 insertions(+), 1 deletion(-)
fs/ext4/fast_commit.c +38 -0
@@ -574,8 +574,14 @@ static int __track_inode(struct inode *inode, void *arg, bool update)return 0 ; } +/* +* Track inode as part of the next fast commit. If the inode is being +* committed, this function will wait for the commit to finish. +*/ void ext4_fc_track_inode (handle_t *handle,struct inode *inode) { +struct ext4_inode_info *ei =EXT4_I (inode); +wait_queue_head_t *wq;struct ext4_sb_info *sbi =EXT4_SB (inode->i_sb);int ret;
@@ -595,6 +601,38 @@ void ext4_fc_track_inode(handle_t *handle, struct inode *inode)if (ext4_test_mount_flag (inode->i_sb,EXT4_MF_FC_INELIGIBLE ))return ; +if (!test_opt2 (inode->i_sb,JOURNAL_FAST_COMMIT ) || + (EXT4_SB (inode->i_sb)->s_mount_state &EXT4_FC_REPLAY ) || +ext4_test_mount_flag (inode->i_sb,EXT4_MF_FC_INELIGIBLE ) || + !list_empty (&ei->i_fc_list)) +return ; + +/* +* If we come here, we may sleep while waiting for the inode to +* commit. We shouldn't be holding i_data_sem in write mode when we go +* to sleep since the commit path needs to grab the lock while +* committing the inode. +*/ +WARN_ON (lockdep_is_held_type (&ei->i_data_sem,1 )); + +while (ext4_test_inode_state (inode,EXT4_STATE_FC_COMMITTING )) { +#if (BITS_PER_LONG <64 ) +DEFINE_WAIT_BIT (wait, &ei->i_state_flags, +EXT4_STATE_FC_COMMITTING ); + wq =bit_waitqueue (&ei->i_state_flags, +EXT4_STATE_FC_COMMITTING ); +#else +DEFINE_WAIT_BIT (wait, &ei->i_flags, +EXT4_STATE_FC_COMMITTING ); + wq =bit_waitqueue (&ei->i_flags, +EXT4_STATE_FC_COMMITTING ); +#endif +prepare_to_wait (wq, &wait.wq_entry,TASK_UNINTERRUPTIBLE ); +if (ext4_test_inode_state (inode,EXT4_STATE_FC_COMMITTING )) +schedule (); +finish_wait (wq, &wait.wq_entry); + } + ret =ext4_fc_track_template (handle, inode, __track_inode,NULL ,1 );trace_ext4_fc_track_inode (handle, inode, ret); }
fs/ext4/inline.c +3 -0
@@ -586,6 +586,7 @@ static int ext4_convert_inline_data_to_extent(struct address_space *mapping, goto out; } +ext4_fc_track_inode (handle, inode); ret =ext4_destroy_inline_data_nolock (handle, inode);if (ret) goto out;
@@ -686,6 +687,7 @@ int ext4_try_to_write_inline_data(struct address_space *mapping, goto convert; } +ext4_fc_track_inode (handle, inode); ret =ext4_journal_get_write_access (handle, inode->i_sb, iloc.bh,EXT4_JTR_NONE );if (ret)
@@ -967,6 +969,7 @@ int ext4_da_write_inline_data_begin(struct address_space *mapping,if (ret <0 ) goto out_release_page; } +ext4_fc_track_inode (handle, inode); ret =ext4_journal_get_write_access (handle, inode->i_sb, iloc.bh,EXT4_JTR_NONE );if (ret)
fs/ext4/inode.c +4 -1
@@ -622,6 +622,7 @@ int ext4_map_blocks(handle_t *handle, struct inode *inode,*/ map->m_flags &= ~EXT4_MAP_FLAGS ; +ext4_fc_track_inode (handle, inode);/* * New blocks allocate and/or writing to unwritten extent * will possibly result in updating i_data, so we take
@@ -4058,7 +4059,7 @@ int ext4_punch_hole(struct file *file, loff_t offset, loff_t length)/* If there are blocks to remove, do it */ if (stop_block > first_block) { - +ext4_fc_track_inode (handle, inode);down_write (&EXT4_I (inode)->i_data_sem);ext4_discard_preallocations (inode,0 );
@@ -4214,6 +4215,7 @@ int ext4_truncate(struct inode *inode)if (err) goto out_stop; +ext4_fc_track_inode (handle, inode);down_write (&EXT4_I (inode)->i_data_sem);ext4_discard_preallocations (inode,0 );
@@ -5734,6 +5736,7 @@ ext4_reserve_inode_write(handle_t *handle, struct inode *inode,brelse (iloc->bh); iloc->bh =NULL ; } +ext4_fc_track_inode (handle, inode); }ext4_std_error (inode->i_sb, err);return err;
Signature · 1 line
2.36.0.rc0.470.gd361397f0d-goog
Jan Kara
reviewerRe: [PATCH v3 2/6] ext4: for committing inode, make ext4_fc_track_inode wait
Quoted 24 lines · Harshad Shirwadkar
From: Harshad Shirwadkar <[email protected]>
If the inode that's being requested to track using
ext4_fc_track_inodeis being committed, then wait until the inode finishes the commit. Also, add calls toext4_fc_track_inodeat the right places.With this patch, now calling
ext4_reserve_inode_write()results in inode being tracked for next fast commit. A subtle lock ordering requirement withi_data_sem(which is documented in the code) requires thatext4_fc_track_inode()be called before grabbingi_data_sem. So, this patch also adds explicitext4_fc_track_inode()calls in places wherei_data_semgrabbed.Signed-off-by Harshad Shirwadkar <[email protected]>--- fs/ext4/fast_commit.c | 38 ++++++++++++++++++++++++++++++++++++++ fs/ext4/inline.c | 3 +++ fs/ext4/inode.c | 5 ++++- 3 files changed, 45 insertions(+), 1 deletion(-)fs/ext4/fast_commit.c +0
-0
fs/ext4/fast_commit.c void ext4_fc_track_inode(handle_t *handle, struct inode *inode) · line 616
Quoted 7 lines
fs/ext4/fast_commit.c +7
-0+/* +* If we come here, we may sleep while waiting for the inode to +* commit. We shouldn't be holding i_data_sem in write mode when we go +* to sleep since the commit path needs to grab the lock while +* committing the inode. +*/ +WARN_ON (lockdep_is_held_type (&ei->i_data_sem,1 ));
Note that we can deadlock even if we had i_data_sem for reading because another reader is not allowed to get the rwsem if there is writer waiting for it. So we need to check even that case here.
Quoted 10 lines
fs/ext4/fast_commit.c +10
-0+while (ext4_test_inode_state (inode,EXT4_STATE_FC_COMMITTING )) { +#if (BITS_PER_LONG <64 ) +DEFINE_WAIT_BIT (wait, &ei->i_state_flags, +EXT4_STATE_FC_COMMITTING ); + wq =bit_waitqueue (&ei->i_state_flags, +EXT4_STATE_FC_COMMITTING ); +#else +DEFINE_WAIT_BIT (wait, &ei->i_flags, +EXT4_STATE_FC_COMMITTING ); + wq = bit_waitqueue(&ei->i_flags,
fs/ext4/fast_commit.c void ext4_fc_track_inode(handle_t *handle, struct inode *inode) · line 637
Quoted 10 lines
fs/ext4/fast_commit.c +8
-0+ EXT4_STATE_FC_COMMITTING); +#endif +prepare_to_wait (wq, &wait.wq_entry,TASK_UNINTERRUPTIBLE ); +if (ext4_test_inode_state (inode,EXT4_STATE_FC_COMMITTING )) +schedule (); +finish_wait (wq, &wait.wq_entry); + } + ret =ext4_fc_track_template (handle, inode, __track_inode,NULL ,1 );trace_ext4_fc_track_inode (handle, inode, ret);
As we discussed in the call we should tell lockdep that this is equivalent to lock+unlock of let's say fc_committing_lock and the fastcommit code setting / clearing EXT4_STATE_FC_COMMITTING is equivalent to lock / unlock of fc_committing_lock. That way we get proper lockdep tracking of this waiting primitive.
Honza
Signature · 2 lines
Jan Kara <[email protected]> SUSE Labs, CR
Re: [PATCH v3 2/6] ext4: for committing inode, make ext4_fc_track_inode wait
Thanks for the review. Some questions / comments below:
Quoted 22 lines · Jan Kara
Quoted 20 lines · Harshad Shirwadkar
From: Harshad Shirwadkar <[email protected]>
If the inode that's being requested to track using
ext4_fc_track_inodeis being committed, then wait until the inode finishes the commit. Also, add calls toext4_fc_track_inodeat the right places.With this patch, now calling
ext4_reserve_inode_write()results in inode being tracked for next fast commit. A subtle lock ordering requirement withi_data_sem(which is documented in the code) requires thatext4_fc_track_inode()be called before grabbingi_data_sem. So, this patch also adds explicitext4_fc_track_inode()calls in places wherei_data_semgrabbed.Signed-off-by Harshad Shirwadkar <[email protected]>--- fs/ext4/fast_commit.c | 38 ++++++++++++++++++++++++++++++++++++++ fs/ext4/inline.c | 3 +++ fs/ext4/inode.c | 5 ++++- 3 files changed, 45 insertions(+), 1 deletion(-)
Quoted 15 lines
fs/ext4/fast_commit.c void ext4_fc_track_inode(handle_t *handle, struct inode *inode) · line 616
Quoted 11 lines
fs/ext4/fast_commit.c +7
-0+/* +* If we come here, we may sleep while waiting for the inode to +* commit. We shouldn't be holding i_data_sem in write mode when we go +* to sleep since the commit path needs to grab the lock while +* committing the inode. +*/ +WARN_ON (lockdep_is_held_type (&ei->i_data_sem,1 ));Note that we can deadlock even if we had
i_data_semfor reading because another reader is not allowed to get the rwsem if there is writer waiting for it. So we need to check even that case here.
I turned the above WARN_ON to check if data_sem is held in either read or write mode and now I am seeing many other places where data_sem gets grabbed in read mode before calling ext4_fc_track_inode(). We either need to call ext4_fc_track_inode() before all ext4_reserve_inode_write() in all those cases, or ensure that places that acquire in data_sem in write mode, wait if there's an ongoing commit and only then lock data_sem.
Quoted 19 lines
Quoted 19 lines
fs/ext4/fast_commit.c +18
-0+while (ext4_test_inode_state (inode,EXT4_STATE_FC_COMMITTING )) { +#if (BITS_PER_LONG <64 ) +DEFINE_WAIT_BIT (wait, &ei->i_state_flags, +EXT4_STATE_FC_COMMITTING ); + wq =bit_waitqueue (&ei->i_state_flags, +EXT4_STATE_FC_COMMITTING ); +#else +DEFINE_WAIT_BIT (wait, &ei->i_flags, +EXT4_STATE_FC_COMMITTING ); + wq =bit_waitqueue (&ei->i_flags, +EXT4_STATE_FC_COMMITTING ); +#endif +prepare_to_wait (wq, &wait.wq_entry,TASK_UNINTERRUPTIBLE ); +if (ext4_test_inode_state (inode,EXT4_STATE_FC_COMMITTING )) +schedule (); +finish_wait (wq, &wait.wq_entry); + } +
Quoted 8 lines
Quoted 2 lines
ret = ext4_fc_track_template(handle, inode, __track_inode, NULL, 1); trace_ext4_fc_track_inode(handle, inode, ret);As we discussed in the call we should tell lockdep that this is equivalent to lock+unlock of let's say
fc_committing_lockand the fastcommit code setting / clearingEXT4_STATE_FC_COMMITTINGis equivalent to lock / unlock offc_committing_lock. That way we get proper lockdep tracking of this waiting primitive.
Sure, so you mean just adding __acquires() / __releases() annotations in these places right?
- Harshad
Quoted 6 lines
Honza
--
Jan Kara <[email protected]>
SUSE Labs, CR
Jan Kara
reviewerRe: [PATCH v3 2/6] ext4: for committing inode, make ext4_fc_track_inode wait
Quoted 38 lines · harshad shirwadkar
Quoted 22 lines · Jan Kara
Quoted 20 lines · Harshad Shirwadkar
From: Harshad Shirwadkar <[email protected]>
If the inode that's being requested to track using
ext4_fc_track_inodeis being committed, then wait until the inode finishes the commit. Also, add calls toext4_fc_track_inodeat the right places.With this patch, now calling
ext4_reserve_inode_write()results in inode being tracked for next fast commit. A subtle lock ordering requirement withi_data_sem(which is documented in the code) requires thatext4_fc_track_inode()be called before grabbingi_data_sem. So, this patch also adds explicitext4_fc_track_inode()calls in places wherei_data_semgrabbed.Signed-off-by Harshad Shirwadkar <[email protected]>--- fs/ext4/fast_commit.c | 38 ++++++++++++++++++++++++++++++++++++++ fs/ext4/inline.c | 3 +++ fs/ext4/inode.c | 5 ++++- 3 files changed, 45 insertions(+), 1 deletion(-)Quoted 15 lines
fs/ext4/fast_commit.c void ext4_fc_track_inode(handle_t *handle, struct inode *inode) · line 616
Quoted 11 lines
fs/ext4/fast_commit.c +7
-0+/* +* If we come here, we may sleep while waiting for the inode to +* commit. We shouldn't be holding i_data_sem in write mode when we go +* to sleep since the commit path needs to grab the lock while +* committing the inode. +*/ +WARN_ON (lockdep_is_held_type (&ei->i_data_sem,1 ));Note that we can deadlock even if we had
i_data_semfor reading because another reader is not allowed to get the rwsem if there is writer waiting for it. So we need to check even that case here.
Quoted 3 lines
I turned the above
WARN_ONto check ifdata_semis held in either read or write mode and now I am seeing many other places wheredata_semgets grabbed in read mode before callingext4_fc_track_inode().
Hum, that's unpleasant. Which places BTW? I'd expect this mostly happens in ext4_map_blocks() paths. Anywhere else?
Quoted 4 lines
We either need to call
ext4_fc_track_inode()before allext4_reserve_inode_write()in all those cases, or ensure that places that acquire indata_semin write mode, wait if there's an ongoing commit and only then lockdata_sem.
Neither is particularly appealing I guess. As we discussed on the call, probably using extent status tree for the fastcommit code might be a cleaner option.
Quoted 26 lines
Quoted 18 lines
Quoted 18 lines
fs/ext4/fast_commit.c +18
-0+while (ext4_test_inode_state (inode,EXT4_STATE_FC_COMMITTING )) { +#if (BITS_PER_LONG <64 ) +DEFINE_WAIT_BIT (wait, &ei->i_state_flags, +EXT4_STATE_FC_COMMITTING ); + wq =bit_waitqueue (&ei->i_state_flags, +EXT4_STATE_FC_COMMITTING ); +#else +DEFINE_WAIT_BIT (wait, &ei->i_flags, +EXT4_STATE_FC_COMMITTING ); + wq =bit_waitqueue (&ei->i_flags, +EXT4_STATE_FC_COMMITTING ); +#endif +prepare_to_wait (wq, &wait.wq_entry,TASK_UNINTERRUPTIBLE ); +if (ext4_test_inode_state (inode,EXT4_STATE_FC_COMMITTING )) +schedule (); +finish_wait (wq, &wait.wq_entry); + } +Quoted 8 lines
Quoted 2 lines
ret = ext4_fc_track_template(handle, inode, __track_inode, NULL, 1); trace_ext4_fc_track_inode(handle, inode, ret);As we discussed in the call we should tell lockdep that this is equivalent to lock+unlock of let's say
fc_committing_lockand the fastcommit code setting / clearingEXT4_STATE_FC_COMMITTINGis equivalent to lock / unlock offc_committing_lock. That way we get proper lockdep tracking of this waiting primitive.
Quoted 2 lines
Sure, so you mean just adding
__acquires()/__releases()annotations in these places right?
No. __acquires() and __releases() are sparse annotations. Sparse does also some lock checking but it is a static checker and is pretty trivial. Here you need to instrument lockdep. We do similar thing in jbd2 to tell lockdep that starting a transaction handle effectively behaves as a lock - see the rwsem_acquire_read() and rwsem_release() in start_this_handle() and stop_this_handle(), respectively.
Honza
Signature · 2 lines
Jan Kara <[email protected]> SUSE Labs, CR
PATCH v3 3/6 ext4: mark inode dirty before grabbing i_data_sem in ext4_setattr
In reply to Harshad ShirwadkarFrom: Harshad Shirwadkar <[email protected]>
Mark inode dirty first and then grab i_data_sem in ext4_setattr().
--- fs/ext4/inode.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-)
fs/ext4/inode.c +3 -2
@@ -5455,11 +5455,12 @@ int ext4_setattr(struct user_namespace *mnt_userns, struct dentry *dentry, (attr->ia_size >0 ? attr->ia_size -1 :0 ) >> inode->i_sb->s_blocksize_bits); -down_write (&EXT4_I (inode)->i_data_sem); -EXT4_I (inode)->i_disksize = attr->ia_size; rc =ext4_mark_inode_dirty (handle, inode);if (!error) error = rc; +down_write (&EXT4_I (inode)->i_data_sem); +EXT4_I (inode)->i_disksize = attr->ia_size; +/* * We have to update i_size under i_data_sem together * with i_disksize to avoid races with writeback code
Signature · 1 line
2.36.0.rc0.470.gd361397f0d-goog
Jan Kara
reviewerRe: [PATCH v3 3/6] ext4: mark inode dirty before grabbing i_data_sem in ext4_setattr
Quoted 12 lines · Harshad Shirwadkar
From: Harshad Shirwadkar <[email protected]>
Mark inode dirty first and then grab
i_data_seminext4_setattr().Signed-off-by Harshad Shirwadkar <[email protected]>fs/ext4/inode.c +0
-0@@ -5455,11 +5455,12 @@ int ext4_setattr(struct user_namespace *mnt_userns, struct dentry *dentry, (attr->ia_size > 0 ? attr->ia_size - 1 : 0) >>
fs/ext4/inode.c int ext4_setattr(struct user_namespace *mnt_userns, struct dentry *dentry, · line 5463
Quoted 10 lines
fs/ext4/inode.c +3
-2inode->i_sb->s_blocksize_bits); -down_write (&EXT4_I (inode)->i_data_sem); -EXT4_I (inode)->i_disksize = attr->ia_size; rc =ext4_mark_inode_dirty (handle, inode);if (!error) error = rc; +down_write (&EXT4_I (inode)->i_data_sem); +EXT4_I (inode)->i_disksize = attr->ia_size; +
Hum, this isn't going to fly because ext4_mark_inode_dirty() copies data from ext4_inode_info to the on-disk buffer and thus new i_disksize will not be stored on the disk after your change.
Honza
Signature · 2 lines
Jan Kara <[email protected]> SUSE Labs, CR
PATCH v3 4/6 ext4: rework fast commit commit path
In reply to Harshad ShirwadkarFrom: Harshad Shirwadkar <[email protected]>
This patch reworks fast commit's commit path to remove locking the journal for the entire duration of a fast commit. Instead, we only lock the journal while marking all the eligible inodes as "committing". This allows handles to make progress in parallel with the fast commit.
--- fs/ext4/fast_commit.c | 71 ++++++++++++++++++++++++++++--------------- fs/jbd2/journal.c | 2 -- 2 files changed, 46 insertions(+), 27 deletions(-)
fs/ext4/fast_commit.c +46 -25
@@ -287,20 +287,30 @@ void ext4_fc_del(struct inode *inode) (EXT4_SB(inode->i_sb)->s_mount_state & EXT4_FC_REPLAY)) return; -restart:spin_lock (&EXT4_SB (inode->i_sb)->s_fc_lock);if (list_empty (&ei->i_fc_list) &&list_empty (&ei->i_fc_dilist)) {spin_unlock (&EXT4_SB (inode->i_sb)->s_fc_lock);return ; } -if (ext4_test_inode_state (inode,EXT4_STATE_FC_COMMITTING )) { -ext4_fc_wait_committing_inode (inode); - goto restart; - } - -if (!list_empty (&ei->i_fc_list)) -list_del_init (&ei->i_fc_list); +/* +* Since ext4_fc_del is called from ext4_evict_inode while having a +* handle open, there is no need for us to wait here even if a fast +* commit is going on. That is because, if this inode is being +* committed, ext4_mark_inode_dirty would have waited for inode commit +* operation to finish before we come here. So, by the time we come +* here, inode's EXT4_STATE_FC_COMMITTING would have been cleared. So, +* we shouldn't see EXT4_STATE_FC_COMMITTING to be set on this inode +* here. +* +* We may come here without any handles open in the "no_delete" case of +* ext4_evict_inode as well. However, if that happens, we first mark the +* file system as fast commit ineligible anyway. So, even in that case, +* it is okay to remove the inode from the fc list. +*/ +WARN_ON (ext4_test_inode_state (inode,EXT4_STATE_FC_COMMITTING ) + && !ext4_test_mount_flag (inode->i_sb,EXT4_MF_FC_INELIGIBLE )); +list_del_init (&ei->i_fc_list);/* * Since this inode is getting removed, let's also remove all FC
@@ -323,8 +333,6 @@ void ext4_fc_del(struct inode *inode) fc_dentry->fcd_name.len > DNAME_INLINE_LEN)kfree (fc_dentry->fcd_name.name);kmem_cache_free (ext4_fc_dentry_cachep, fc_dentry); - -return ; }/*
@@ -1013,19 +1021,6 @@ static int ext4_fc_submit_inode_data_all(journal_t *journal)spin_lock (&sbi->s_fc_lock);list_for_each_entry (ei, &sbi->s_fc_q[FC_Q_MAIN ], i_fc_list) { -ext4_set_inode_state (&ei->vfs_inode,EXT4_STATE_FC_COMMITTING ); -while (atomic_read (&ei->i_fc_updates)) { -DEFINE_WAIT (wait); - -prepare_to_wait (&ei->i_fc_wait, &wait, -TASK_UNINTERRUPTIBLE ); -if (atomic_read (&ei->i_fc_updates)) { -spin_unlock (&sbi->s_fc_lock); -schedule (); -spin_lock (&sbi->s_fc_lock); - } -finish_wait (&ei->i_fc_wait, &wait); - }spin_unlock (&sbi->s_fc_lock); ret =jbd2_submit_inode_data (ei->jinode);if (ret)
@@ -1138,6 +1133,16 @@ static int ext4_fc_perform_commit(journal_t *journal)int ret =0 ;u32 crc =0 ; +/* Lock the journal */ +jbd2_journal_lock_updates (journal); +spin_lock (&sbi->s_fc_lock); +list_for_each_entry (iter, &sbi->s_fc_q[FC_Q_MAIN ], i_fc_list) { +ext4_set_inode_state (&iter->vfs_inode, +EXT4_STATE_FC_COMMITTING ); + } +spin_unlock (&sbi->s_fc_lock); +jbd2_journal_unlock_updates (journal); + ret =ext4_fc_submit_inode_data_all (journal);if (ret)return ret;
@@ -1188,6 +1193,18 @@ static int ext4_fc_perform_commit(journal_t *journal) ret =ext4_fc_write_inode (inode, &crc);if (ret) goto out; +ext4_clear_inode_state (inode,EXT4_STATE_FC_COMMITTING ); +/* +* Make sure clearing of EXT4_STATE_FC_COMMITTING is +* visible before we send the wakeup. Pairs with implicit +* barrier in prepare_to_wait() in ext4_fc_track_inode(). +*/ +smp_mb (); +#if (BITS_PER_LONG <64 ) +wake_up_bit (&iter->i_state_flags,EXT4_STATE_FC_COMMITTING ); +#else +wake_up_bit (&iter->i_flags,EXT4_STATE_FC_COMMITTING ); +#endif spin_lock (&sbi->s_fc_lock); }spin_unlock (&sbi->s_fc_lock);
@@ -1325,13 +1342,17 @@ static void ext4_fc_cleanup(journal_t *journal, int full, tid_t tid)spin_lock (&sbi->s_fc_lock);list_for_each_entry_safe (iter, iter_n, &sbi->s_fc_q[FC_Q_MAIN ], i_fc_list) { -list_del_init (&iter->i_fc_list);ext4_clear_inode_state (&iter->vfs_inode,EXT4_STATE_FC_COMMITTING );if (iter->i_sync_tid <= tid)ext4_fc_reset_inode (&iter->vfs_inode); -/* Make sure EXT4_STATE_FC_COMMITTING bit is clear */ +/* +* Make sure clearing of EXT4_STATE_FC_COMMITTING is +* visible before we send the wakeup. Pairs with implicit +* barrier in prepare_to_wait() in ext4_fc_track_inode(). +*/ smp_mb (); +list_del_init (&iter->i_fc_list);#if (BITS_PER_LONG <64 )wake_up_bit (&iter->i_state_flags,EXT4_STATE_FC_COMMITTING );#else
fs/jbd2/journal.c +0 -2
@@ -757,7 +757,6 @@ int jbd2_fc_begin_commit(journal_t *journal, tid_t tid) } journal->j_flags |=JBD2_FAST_COMMIT_ONGOING ;write_unlock (&journal->j_state_lock); -jbd2_journal_lock_updates (journal);return 0 ; }
@@ -769,7 +768,6 @@ EXPORT_SYMBOL(jbd2_fc_begin_commit);*/ static int __jbd2_fc_end_commit (journal_t *journal,tid_t tid,bool fallback) { -jbd2_journal_unlock_updates (journal);if (journal->j_fc_cleanup_callback) journal->j_fc_cleanup_callback (journal,0 , tid);write_lock (&journal->j_state_lock);
Signature · 1 line
2.36.0.rc0.470.gd361397f0d-goog
PATCH v3 5/6 ext4: drop i_fc_updates from inode fc info
In reply to Harshad ShirwadkarFrom: Harshad Shirwadkar <[email protected]>
The new logic introduced in this series does not require tracking number of active handles open on an inode. So, drop it.
--- fs/ext4/ext4.h | 5 ---- fs/ext4/fast_commit.c | 70 ------------------------------------------- 2 files changed, 75 deletions(-)
fs/ext4/ext4.h +0 -5
@@ -1059,9 +1059,6 @@ struct ext4_inode_info {/* End of lblk range that needs to be committed in this fast commit */ ext4_lblk_t i_fc_lblk_len; -/* Number of ongoing updates on this inode */ -atomic_t i_fc_updates; -/* Fast commit wait queue for this inode */ wait_queue_head_t i_fc_wait;
@@ -2930,8 +2927,6 @@ void __ext4_fc_track_create(handle_t *handle, struct inode *inode,void ext4_fc_track_create (handle_t *handle,struct dentry *dentry);void ext4_fc_track_inode (handle_t *handle,struct inode *inode);void ext4_fc_mark_ineligible (struct super_block *sb,int reason,handle_t *handle); -void ext4_fc_start_update (struct inode *inode); -void ext4_fc_stop_update (struct inode *inode);void ext4_fc_del (struct inode *inode);bool ext4_fc_replay_check_excluded (struct super_block *sb,ext4_fsblk_t block);void ext4_fc_replay_cleanup (struct super_block *sb);
fs/ext4/fast_commit.c +0 -70
76 lines not on this page · raw message
Signature · 1 line
2.36.0.rc0.470.gd361397f0d-goog
PATCH v3 6/6 ext4: update code documentation
In reply to Harshad ShirwadkarFrom: Harshad Shirwadkar <[email protected]>
This patch updates code documentation to reflect the commit path changes made in this series.
--- fs/ext4/fast_commit.c | 39 ++++++++++++++++++++++++++------------- 1 file changed, 26 insertions(+), 13 deletions(-)
fs/ext4/fast_commit.c +26 -13
@@ -49,14 +49,21 @@* that need to be committed during a fast commit in another in memory queue of * inodes. During the commit operation, we commit in the following order: * -* [1] Lock inodes for any further data updates by setting COMMITTING state -* [2] Submit data buffers of all the inodes -* [3] Wait for [2] to complete -* [4] Commit all the directory entry updates in the fast commit space -* [5] Commit all the changed inode structures -* [6] Write tail tag (this tag ensures the atomicity, please read the following +* [1] Lock the journal by calling jbd2_journal_lock_updates. This ensures that +* all the exsiting handles finish and no new handles can start. +* [2] Mark all the fast commit eligible inodes as undergoing fast commit +* by setting "EXT4_STATE_FC_COMMITTING" state. +* [3] Unlock the journal by calling jbd2_journal_unlock_updates. This allows +* starting of new handles. If new handles try to start an update on +* any of the inodes that are being committed, ext4_fc_track_inode() +* will block until those inodes have finished the fast commit. +* [4] Submit data buffers of all the committing inodes. +* [5] Wait for [4] to complete. +* [6] Commit all the directory entry updates in the fast commit space. +* [7] Commit all the changed inodes in the fast commit space and clear +* "EXT4_STATE_FC_COMMITTING" for these inodes. +* [8] Write tail tag (this tag ensures the atomicity, please read the following * section for more details). -* [7] Wait for [4], [5] and [6] to complete. * * All the inode updates must call ext4_fc_start_update() before starting an * update. If such an ongoing update is present, fast commit waits for it to
@@ -142,6 +149,13 @@* similarly. Thus, by converting a non-idempotent procedure into a series of * idempotent outcomes, fast commits ensured idempotence during the replay. * +* Locking +* ------- +* sbi->s_fc_lock protects the fast commit inodes queue and the fast commit +* dentry queue. ei->i_fc_lock protects the fast commit related info in a given +* inode. Most of the code avoids acquiring both the locks, but if one must do +* that then sbi->s_fc_lock must be acquired before ei->i_fc_lock. +* * TODOs * ----- *
@@ -156,13 +170,12 @@* fast commit recovery even if that area is invalidated by later full * commits. * -* 1) Fast commit's commit path locks the entire file system during fast -* commit. This has significant performance penalty. Instead of that, we -* should use ext4_fc_start/stop_update functions to start inode level -* updates from ext4_journal_start/stop. Once we do that we can drop file -* system locking during commit path. +* 1) Handle more ineligible cases. * -* 2) Handle more ineligible cases. +* 2) Change ext4_fc_commit() to lookup logical to physical mapping using extent +* status tree. This would get rid of the need to call ext4_fc_track_inode() +* before acquiring i_data_sem. To do that we would need to ensure that +* modified extents from the extent status tree are not evicted from memory. */ #include <trace/events/ext4.h>
Signature · 1 line
2.36.0.rc0.470.gd361397f0d-goog