From: Ritesh Harjani (IBM) <ritesh.list@gmail.com>
To: Kemeng Shi <shikemeng@huaweicloud.com>,
tytso@mit.edu, adilger.kernel@dilger.ca, ojaswin@linux.ibm.com,
linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: shikemeng@huaweicloud.com
Subject: Re: [PATCH v3 10/10] ext4: correct some stale comment of criteria
Date: Wed, 02 Aug 2023 06:48:52 +0530 [thread overview]
Message-ID: <87v8dyw8ar.fsf@doe.com> (raw)
In-Reply-To: <20230801143204.2284343-11-shikemeng@huaweicloud.com>
Kemeng Shi <shikemeng@huaweicloud.com> writes:
> We named criteria with CR_XXX, correct stale comment to criteria with
> raw number.
>
> Signed-off-by: Kemeng Shi <shikemeng@huaweicloud.com>
> ---
> fs/ext4/mballoc.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
> index bfaab173a3f4..1e8ce0ece47a 100644
> --- a/fs/ext4/mballoc.c
> +++ b/fs/ext4/mballoc.c
> @@ -2782,8 +2782,8 @@ ext4_mb_regular_allocator(struct ext4_allocation_context *ac)
>
> /*
> * ac->ac_2order is set only if the fe_len is a power of 2
> - * if ac->ac_2order is set we also set criteria to 0 so that we
> - * try exact allocation using buddy.
> + * if ac->ac_2order is set we also set criteria to CR_POWER2_ALIGNED
> + * so that we try exact allocation using buddy.
> */
> i = fls(ac->ac_g_ex.fe_len);
> ac->ac_2order = 0;
> @@ -2840,8 +2840,8 @@ ext4_mb_regular_allocator(struct ext4_allocation_context *ac)
> /*
> * Batch reads of the block allocation bitmaps
> * to get multiple READs in flight; limit
> - * prefetching at cr=0/1, otherwise mballoc can
> - * spend a lot of time loading imperfect groups
> + * prefetching at inexpensive CR, otherwise mballoc
> + * can spend a lot of time loading imperfect groups
> */
> if ((prefetch_grp == group) &&
> (ext4_mb_cr_expensive(cr) ||
Is this function defined at any place ^^^
-ritesh
next prev parent reply other threads:[~2023-08-02 1:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 14:31 [PATCH v3 00/10] A few fixes and cleanups to mballoc Kemeng Shi
2023-08-01 14:31 ` [PATCH v3 01/10] ext4: correct grp validation in ext4_mb_good_group Kemeng Shi
2023-08-01 14:31 ` [PATCH v3 02/10] ext4: avoid potential data overflow in next_linear_group Kemeng Shi
2023-08-01 14:31 ` [PATCH v3 03/10] ext4: return found group directly in ext4_mb_choose_next_group_p2_aligned Kemeng Shi
2023-08-01 14:31 ` [PATCH v3 04/10] ext4: use is_power_of_2 helper in ext4_mb_regular_allocator Kemeng Shi
2023-08-01 14:31 ` [PATCH v3 05/10] ext4: remove unnecessary return for void function Kemeng Shi
2023-08-01 14:32 ` [PATCH v3 06/10] ext4: replace the traditional ternary conditional operator with with max()/min() Kemeng Shi
2023-08-01 14:32 ` [PATCH v3 07/10] ext4: remove unused ext4_{set}/{clear}_bit_atomic Kemeng Shi
2023-08-01 14:32 ` [PATCH v3 08/10] ext4: return found group directly in ext4_mb_choose_next_group_goal_fast Kemeng Shi
2023-08-01 14:32 ` [PATCH v3 09/10] ext4: return found group directly in ext4_mb_choose_next_group_best_avail Kemeng Shi
2023-08-01 14:32 ` [PATCH v3 10/10] ext4: correct some stale comment of criteria Kemeng Shi
2023-08-02 1:18 ` Ritesh Harjani [this message]
2023-08-02 1:25 ` Ritesh Harjani
2023-08-02 1:25 ` Kemeng Shi
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=87v8dyw8ar.fsf@doe.com \
--to=ritesh.list@gmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojaswin@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