From: Ojaswin Mujoo <ojaswin@linux.ibm.com>
To: linux-ext4@vger.kernel.org, "Theodore Ts'o" <tytso@mit.edu>
Cc: Ritesh Harjani <riteshh@linux.ibm.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Jan Kara <jack@suse.cz>, Kemeng Shi <shikemeng@huaweicloud.com>,
Ritesh Harjani <ritesh.list@gmail.com>
Subject: [PATCH 07/13] ext4: Add counter to track successful allocation of goal length
Date: Thu, 25 May 2023 17:03:01 +0530 [thread overview]
Message-ID: <51cc5ea958b734057a8b31289f6973edec8ab3e4.1685009579.git.ojaswin@linux.ibm.com> (raw)
In-Reply-To: <cover.1685009579.git.ojaswin@linux.ibm.com>
Track number of allocations where the length of blocks allocated is equal to the
length of goal blocks (post normalization). This metric could be useful if
making changes to the allocator logic in the future as it could give us
visibility into how often do we trim our requests.
PS: ac_b_ex.fe_len might get modified due to preallocation efforts and
hence we use ac_f_ex.fe_len instead since we want to compare how much the
allocator was able to actually find.
Signed-off-by: Ojaswin Mujoo <ojaswin@linux.ibm.com>
Reviewed-by: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
Reviewed-by: Jan Kara <jack@suse.cz>
---
fs/ext4/ext4.h | 1 +
fs/ext4/mballoc.c | 3 +++
2 files changed, 4 insertions(+)
diff --git a/fs/ext4/ext4.h b/fs/ext4/ext4.h
index 7b460a31ac82..8bb1edcd2dda 100644
--- a/fs/ext4/ext4.h
+++ b/fs/ext4/ext4.h
@@ -1556,6 +1556,7 @@ struct ext4_sb_info {
atomic_t s_bal_cX_ex_scanned[EXT4_MB_NUM_CRS]; /* total extents scanned */
atomic_t s_bal_groups_scanned; /* number of groups scanned */
atomic_t s_bal_goals; /* goal hits */
+ atomic_t s_bal_len_goals; /* len goal hits */
atomic_t s_bal_breaks; /* too long searches */
atomic_t s_bal_2orders; /* 2^order hits */
atomic_t s_bal_cr0_bad_suggestions;
diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
index 98d93d2c5401..8786aa0dd57a 100644
--- a/fs/ext4/mballoc.c
+++ b/fs/ext4/mballoc.c
@@ -2962,6 +2962,7 @@ int ext4_seq_mb_stats_show(struct seq_file *seq, void *offset)
atomic64_read(&sbi->s_bal_cX_failed[CR3]));
seq_printf(seq, "\textents_scanned: %u\n", atomic_read(&sbi->s_bal_ex_scanned));
seq_printf(seq, "\t\tgoal_hits: %u\n", atomic_read(&sbi->s_bal_goals));
+ seq_printf(seq, "\t\tlen_goal_hits: %u\n", atomic_read(&sbi->s_bal_len_goals));
seq_printf(seq, "\t\t2^n_hits: %u\n", atomic_read(&sbi->s_bal_2orders));
seq_printf(seq, "\t\tbreaks: %u\n", atomic_read(&sbi->s_bal_breaks));
seq_printf(seq, "\t\tlost: %u\n", atomic_read(&sbi->s_mb_lost_chunks));
@@ -4407,6 +4408,8 @@ static void ext4_mb_collect_stats(struct ext4_allocation_context *ac)
if (ac->ac_g_ex.fe_start == ac->ac_b_ex.fe_start &&
ac->ac_g_ex.fe_group == ac->ac_b_ex.fe_group)
atomic_inc(&sbi->s_bal_goals);
+ if (ac->ac_f_ex.fe_len == ac->ac_g_ex.fe_len)
+ atomic_inc(&sbi->s_bal_len_goals);
if (ac->ac_found > sbi->s_mb_max_to_scan)
atomic_inc(&sbi->s_bal_breaks);
}
--
2.31.1
next prev parent reply other threads:[~2023-05-25 11:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-25 11:32 [PATCH 00/13] multiblock allocator improvements Ojaswin Mujoo
2023-05-25 11:32 ` [PATCH 01/13] Revert "ext4: remove ac->ac_found > sbi->s_mb_min_to_scan dead check in ext4_mb_check_limits" Ojaswin Mujoo
2023-05-25 12:24 ` Kemeng Shi
2023-06-02 13:41 ` Linux regression tracking #adding (Thorsten Leemhuis)
2023-05-25 11:32 ` [PATCH 02/13] ext4: mballoc: Remove useless setting of ac_criteria Ojaswin Mujoo
2023-05-25 11:32 ` [PATCH 03/13] ext4: Remove unused extern variables declaration Ojaswin Mujoo
2023-05-25 11:32 ` [PATCH 04/13] ext4: Fix a small typo in ext4_mb_prefetch_fini() Ojaswin Mujoo
2023-05-25 11:32 ` [PATCH 05/13] ext4: Convert mballoc cr (criteria) to enum Ojaswin Mujoo
2023-05-25 11:33 ` [PATCH 06/13] ext4: Add per CR extent scanned counter Ojaswin Mujoo
2023-05-25 11:33 ` Ojaswin Mujoo [this message]
2023-05-25 11:33 ` [PATCH 08/13] ext4: Avoid scanning smaller extents in BG during CR1 Ojaswin Mujoo
2023-05-25 11:33 ` [PATCH 09/13] ext4: Don't skip prefetching BLOCK_UNINIT groups Ojaswin Mujoo
2023-05-25 11:33 ` [PATCH 10/13] ext4: Ensure ext4_mb_prefetch_fini() is called for all prefetched BGs Ojaswin Mujoo
2023-05-25 11:33 ` [PATCH 11/13] ext4: Abstract out logic to search average fragment list Ojaswin Mujoo
2023-05-25 11:33 ` [PATCH 12/13] ext4: Add allocation criteria 1.5 (CR1_5) Ojaswin Mujoo
2023-05-25 11:33 ` [PATCH 13/13] ext4: Give symbolic names to mballoc criterias Ojaswin Mujoo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51cc5ea958b734057a8b31289f6973edec8ab3e4.1685009579.git.ojaswin@linux.ibm.com \
--to=ojaswin@linux.ibm.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ritesh.list@gmail.com \
--cc=riteshh@linux.ibm.com \
--cc=shikemeng@huaweicloud.com \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).