jbd2: Fix leaked transaction credits
Jan Kara
reviewerv2 cover jbd2: Fix leaked transaction credits
Hello,
after debugging more the reason why fsmark run is slower in dioread_nolock mode (which became the default in 5.6), I've found jbd2 actually leaks reserved credits if we start a transaction with reserved handle and then don't use it. The first patch in the series is a small (and independent) cleanup in the area, the second patch fixes the leak.
Then there was another revelation for me that in this workload ext4 actually starts lots of reserved transaction handles that are unused. This is due to the way how ext4 writepages code works - it starts a transaction, then inspects page cache and writes one extent if found. Then starts again a transaction and checks whether there's more to write. So for single extent files we always start transaction twice, second time only to find there's nothing more to write. In case all blocks are already allocated, we wouldn't even have to start transaction at all. This probably also deserves to be fixed but a simple fix I made seems to break page writeback so I need to dig more into it and I want to push out the obvious jbd2 fix early.
Changes since v1:
* Add reviewed-by tag
* Fixed up one coding style issue pointed out by Andreas
Honza
Jan Kara
reviewerPATCH v2 1/2 ext4: Drop ext4_journal_free_reserved()
Remove ext4_journal_free_reserved() function. It is never used.
--- fs/ext4/ext4_jbd2.h | 6 ------ 1 file changed, 6 deletions(-)
fs/ext4/ext4_jbd2.h +0 -6
@@ -335,12 +335,6 @@ static inline handle_t *__ext4_journal_start(struct inode *inode,handle_t *__ext4_journal_start_reserved (handle_t *handle,unsigned int line,int type); -static inline void ext4_journal_free_reserved (handle_t *handle) -{ -if (ext4_handle_valid (handle)) -jbd2_journal_free_reserved (handle); -} -static inline handle_t *ext4_journal_current_handle (void ) {return journal_current_handle ();
Signature · 1 line
2.16.4
Jan Kara
reviewerPATCH v2 2/2 jbd2: Avoid leaking transaction credits when unreserving handle
In reply to Jan KaraWhen reserved transaction handle is unused, we subtract its reserved credits in __jbd2_journal_unreserve_handle() called from jbd2_journal_stop(). However this function forgets to remove reserved credits from transaction->t_outstanding_credits and thus the transaction space that was reserved remains effectively leaked. The leaked transaction space can be quite significant in some cases and leads to unnecessarily small transactions and thus reducing throughput of the journalling machinery. E.g. fsmark workload creating lots of 4k files was observed to have about 20% lower throughput due to this when ext4 is mounted with dioread_nolock mount option.
Subtract reserved credits from t_outstanding_credits as well.
--- fs/jbd2/transaction.c | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-)
fs/jbd2/transaction.c +11 -3
@@ -541,17 +541,24 @@ handle_t *jbd2_journal_start(journal_t *journal, int nblocks) }EXPORT_SYMBOL (jbd2_journal_start); -static void __jbd2_journal_unreserve_handle (handle_t *handle) +static void __jbd2_journal_unreserve_handle (handle_t *handle,transaction_t *t) {journal_t *journal = handle->h_journal;WARN_ON (!handle->h_reserved);sub_reserved_credits (journal, handle->h_total_credits); +if (t) +atomic_sub (handle->h_total_credits, &t->t_outstanding_credits); }void jbd2_journal_free_reserved (handle_t *handle) { -__jbd2_journal_unreserve_handle (handle); +journal_t *journal = handle->h_journal; + +/* Get j_state_lock to pin running transaction if it exists */ +read_lock (&journal->j_state_lock); +__jbd2_journal_unreserve_handle (handle, journal->j_running_transaction); +read_unlock (&journal->j_state_lock);jbd2_free_handle (handle); }EXPORT_SYMBOL (jbd2_journal_free_reserved);
@@ -722,7 +729,8 @@ static void stop_this_handle(handle_t *handle)atomic_sub (handle->h_total_credits, &transaction->t_outstanding_credits);if (handle->h_rsv_handle) -__jbd2_journal_unreserve_handle (handle->h_rsv_handle); +__jbd2_journal_unreserve_handle (handle->h_rsv_handle, + transaction);if (atomic_dec_and_test (&transaction->t_updates))wake_up (&journal->j_wait_updates);
Signature · 1 line
2.16.4
Re: [PATCH 1/2] ext4: Drop ext4_journal_free_reserved()
In reply to Jan KaraQuoted 4 lines · Jan Kara
Remove
ext4_journal_free_reserved()function. It is never used.Signed-off-by Jan Kara <[email protected]>
Quoted 22 lines
---
fs/ext4/ext4_jbd2.h| 6 ------1 file changed, 6 deletions(-)fs/ext4/ext4_jbd2.h +0
-7@@ -335,12 +335,6 @@ static inline handle_t *__ext4_journal_start(struct inode *inode,handle_t *__ext4_journal_start_reserved (handle_t *handle,unsigned int line,int type); -static inline void ext4_journal_free_reserved (handle_t *handle) -{ -if (ext4_handle_valid (handle)) -jbd2_journal_free_reserved (handle); -} -static inline handle_t *ext4_journal_current_handle (void ) {return journal_current_handle (); --
Quoted 2 lines
2.16.4
Cheers, Andreas
Re: [PATCH 1/2] ext4: Drop ext4_journal_free_reserved()
Quoted 7 lines · Andreas Dilger
Quoted 4 lines · Jan Kara
Remove
ext4_journal_free_reserved()function. It is never used.Signed-off-by Jan Kara <[email protected]>Reviewed-by Andreas Dilger <[email protected]>
Thanks, applied.
- Ted
Re: [PATCH 2/2] jbd2: Avoid leaking transaction credits when unreserving handle
In reply to Jan KaraQuoted 11 lines · Jan Kara
When reserved transaction handle is unused, we subtract its reserved credits in
__jbd2_journal_unreserve_handle()called fromjbd2_journal_stop(). However this function forgets to remove reserved credits fromtransaction->t_outstanding_creditsand thus the transaction space that was reserved remains effectively leaked. The leaked transaction space can be quite significant in some cases and leads to unnecessarily small transactions and thus reducing throughput of the journalling machinery. E.g. fsmark workload creating lots of 4k files was observed to have about 20% lower throughput due to this when ext4 is mounted withdioread_nolockmount option.
Quoted 6 lines
Subtract reserved credits from
t_outstanding_creditsas well.Fixes 8f7d89f36829 ("jbd2: transaction reservation support")Reviewed-by Andreas Dilger <[email protected]>Signed-off-by Jan Kara <[email protected]>
Thanks, applied.
- Ted