From: hanjinke <hanjinke.666@bytedance.com>
To: tytso@mit.edu, adilger.kernel@dilger.ca
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org,
lei.rao@intel.com
Subject: Re: [PATCH] ext4: reuse order and buddy in mb_mark_used when buddy split
Date: Tue, 21 Jun 2022 10:40:30 +0800 [thread overview]
Message-ID: <2a95ca55-4088-583b-9a28-cf9f4c0f32fc@bytedance.com> (raw)
In-Reply-To: <20220606155305.74146-1-hanjinke.666@bytedance.com>
hi, friendly pinging...
在 2022/6/6 下午11:53, Jinke Han 写道:
> From: hanjinke <hanjinke.666@bytedance.com>
>
> After each buddy split, mb_mark_used will search the proper order
> for the block which may consume some loop in mb_find_order_for_block.
> In fact, we can reuse the oder and buddy generated by the buddy split.
>
> Reviewed by: lei.rao@intel.com
> Signed-off-by: hanjinke <hanjinke.666@bytedance.com>
> ---
> fs/ext4/mballoc.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/fs/ext4/mballoc.c b/fs/ext4/mballoc.c
> index 9f12f29bc346..c7ac6b269dd8 100644
> --- a/fs/ext4/mballoc.c
> +++ b/fs/ext4/mballoc.c
> @@ -1933,6 +1933,7 @@ static int mb_mark_used(struct ext4_buddy *e4b, struct ext4_free_extent *ex)
> unsigned ret = 0;
> int len0 = len;
> void *buddy;
> + bool split = false;
>
> BUG_ON(start + len > (e4b->bd_sb->s_blocksize << 3));
> BUG_ON(e4b->bd_group != ex->fe_group);
> @@ -1957,12 +1958,16 @@ static int mb_mark_used(struct ext4_buddy *e4b, struct ext4_free_extent *ex)
>
> /* let's maintain buddy itself */
> while (len) {
> - ord = mb_find_order_for_block(e4b, start);
> + if (!split)
> + ord = mb_find_order_for_block(e4b, start);
>
> if (((start >> ord) << ord) == start && len >= (1 << ord)) {
> /* the whole chunk may be allocated at once! */
> mlen = 1 << ord;
> - buddy = mb_find_buddy(e4b, ord, &max);
> + if (!split)
> + buddy = mb_find_buddy(e4b, ord, &max);
> + else
> + split = false;
> BUG_ON((start >> ord) >= max);
> mb_set_bit(start >> ord, buddy);
> e4b->bd_info->bb_counters[ord]--;
> @@ -1989,6 +1994,7 @@ static int mb_mark_used(struct ext4_buddy *e4b, struct ext4_free_extent *ex)
> mb_clear_bit(cur + 1, buddy);
> e4b->bd_info->bb_counters[ord]++;
> e4b->bd_info->bb_counters[ord]++;
> + split = true;
> }
> mb_set_largest_free_order(e4b->bd_sb, e4b->bd_info);
>
next prev parent reply other threads:[~2022-06-21 2:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 15:53 Jinke Han
2022-06-21 2:40 ` hanjinke [this message]
2022-07-08 3:19 ` Theodore Ts'o
-- strict thread matches above, loose matches on Subject: below --
2022-06-06 15:51 Jinke Han
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=2a95ca55-4088-583b-9a28-cf9f4c0f32fc@bytedance.com \
--to=hanjinke.666@bytedance.com \
--cc=adilger.kernel@dilger.ca \
--cc=lei.rao@intel.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®