From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Yi Sun <yi.sun@unisoc.com>
Cc: chao@kernel.org, sunyibuaa@gmail.com,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, niuzhiguo84@gmail.com,
Hao_hao.Wang@unisoc.com, ke.wang@unisoc.com
Subject: Re: [PATCH v3 3/5] f2fs: introduce update_sit_entry_for_release()
Date: Fri, 20 Dec 2024 21:22:08 +0000 [thread overview]
Message-ID: <Z2XgAMRm6uMAT2XM@google.com> (raw)
In-Reply-To: <20241104034545.497907-4-yi.sun@unisoc.com>
This makes the code being inconsistent. Can you refactor first and add the loop
later separately?
For example,
1) add two functions, update_sit_entry_for_alloc() and update_sit_entry_for_release()
2) add a loop in update_sit_entry_for_release()
Thanks,
On 11/04, Yi Sun wrote:
> This function can process some consecutive blocks at a time.
>
> When using update_sit_entry() to release consecutive blocks,
> ensure that the consecutive blocks belong to the same segment.
> Because after update_sit_entry_for_realese(), @segno is still
> in use in update_sit_entry().
>
> Signed-off-by: Yi Sun <yi.sun@unisoc.com>
> ---
> fs/f2fs/segment.c | 103 ++++++++++++++++++++++++++++++----------------
> 1 file changed, 68 insertions(+), 35 deletions(-)
>
> diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
> index 5386ae18d808..843171ce414b 100644
> --- a/fs/f2fs/segment.c
> +++ b/fs/f2fs/segment.c
> @@ -2424,6 +2424,70 @@ static void update_segment_mtime(struct f2fs_sb_info *sbi, block_t blkaddr,
> SIT_I(sbi)->max_mtime = ctime;
> }
>
> +/*
> + * NOTE: when updating multiple blocks at the same time, please ensure
> + * that the consecutive input blocks belong to the same segment.
> + */
> +
> +static int update_sit_entry_for_release(struct f2fs_sb_info *sbi, struct seg_entry *se,
> + block_t blkaddr, unsigned int offset, int del)
> +{
> + bool exist;
> +#ifdef CONFIG_F2FS_CHECK_FS
> + bool mir_exist;
> +#endif
> + int i;
> + int del_count = -del;
> +
> + f2fs_bug_on(sbi, GET_SEGNO(sbi, blkaddr) != GET_SEGNO(sbi, blkaddr + del_count - 1));
> +
> + for (i = 0; i < del_count; i++) {
> + exist = f2fs_test_and_clear_bit(offset + i, se->cur_valid_map);
> +#ifdef CONFIG_F2FS_CHECK_FS
> + mir_exist = f2fs_test_and_clear_bit(offset + i,
> + se->cur_valid_map_mir);
> + if (unlikely(exist != mir_exist)) {
> + f2fs_err(sbi, "Inconsistent error when clearing bitmap, blk:%u, old bit:%d",
> + blkaddr + i, exist);
> + f2fs_bug_on(sbi, 1);
> + }
> +#endif
> + if (unlikely(!exist)) {
> + f2fs_err(sbi, "Bitmap was wrongly cleared, blk:%u",
> + blkaddr + i);
> + f2fs_bug_on(sbi, 1);
> + se->valid_blocks++;
> + del += 1;
> + } else if (unlikely(is_sbi_flag_set(sbi, SBI_CP_DISABLED))) {
> + /*
> + * If checkpoints are off, we must not reuse data that
> + * was used in the previous checkpoint. If it was used
> + * before, we must track that to know how much space we
> + * really have.
> + */
> + if (f2fs_test_bit(offset + i, se->ckpt_valid_map)) {
> + spin_lock(&sbi->stat_lock);
> + sbi->unusable_block_count++;
> + spin_unlock(&sbi->stat_lock);
> + }
> + }
> +
> + if (f2fs_block_unit_discard(sbi) &&
> + f2fs_test_and_clear_bit(offset + i, se->discard_map))
> + sbi->discard_blks++;
> +
> + if (!f2fs_test_bit(offset + i, se->ckpt_valid_map))
> + se->ckpt_valid_blocks -= 1;
> + }
> +
> + return del;
> +}
> +
> +/*
> + * If releasing blocks, this function supports updating multiple consecutive blocks
> + * at one time, but please note that these consecutive blocks need to belong to the
> + * same segment.
> + */
> static void update_sit_entry(struct f2fs_sb_info *sbi, block_t blkaddr, int del)
> {
> struct seg_entry *se;
> @@ -2479,43 +2543,12 @@ static void update_sit_entry(struct f2fs_sb_info *sbi, block_t blkaddr, int del)
> if (!f2fs_test_and_set_bit(offset, se->ckpt_valid_map))
> se->ckpt_valid_blocks++;
> }
> - } else {
> - exist = f2fs_test_and_clear_bit(offset, se->cur_valid_map);
> -#ifdef CONFIG_F2FS_CHECK_FS
> - mir_exist = f2fs_test_and_clear_bit(offset,
> - se->cur_valid_map_mir);
> - if (unlikely(exist != mir_exist)) {
> - f2fs_err(sbi, "Inconsistent error when clearing bitmap, blk:%u, old bit:%d",
> - blkaddr, exist);
> - f2fs_bug_on(sbi, 1);
> - }
> -#endif
> - if (unlikely(!exist)) {
> - f2fs_err(sbi, "Bitmap was wrongly cleared, blk:%u",
> - blkaddr);
> - f2fs_bug_on(sbi, 1);
> - se->valid_blocks++;
> - del = 0;
> - } else if (unlikely(is_sbi_flag_set(sbi, SBI_CP_DISABLED))) {
> - /*
> - * If checkpoints are off, we must not reuse data that
> - * was used in the previous checkpoint. If it was used
> - * before, we must track that to know how much space we
> - * really have.
> - */
> - if (f2fs_test_bit(offset, se->ckpt_valid_map)) {
> - spin_lock(&sbi->stat_lock);
> - sbi->unusable_block_count++;
> - spin_unlock(&sbi->stat_lock);
> - }
> - }
>
> - if (f2fs_block_unit_discard(sbi) &&
> - f2fs_test_and_clear_bit(offset, se->discard_map))
> - sbi->discard_blks++;
> + if (!f2fs_test_bit(offset, se->ckpt_valid_map))
> + se->ckpt_valid_blocks += del;
> + } else {
> + del = update_sit_entry_for_release(sbi, se, blkaddr, offset, del);
> }
> - if (!f2fs_test_bit(offset, se->ckpt_valid_map))
> - se->ckpt_valid_blocks += del;
>
> __mark_sit_entry_dirty(sbi, segno);
>
> --
> 2.25.1
next prev parent reply other threads:[~2024-12-20 21:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-04 3:45 [PATCH v3 0/5] Speed up f2fs truncate Yi Sun
2024-11-04 3:45 ` [PATCH v3 1/5] f2fs: expand f2fs_invalidate_compress_page() to f2fs_invalidate_compress_pages_range() Yi Sun
2024-11-04 3:45 ` [PATCH v3 2/5] f2fs: add parameter @len to f2fs_invalidate_internal_cache() Yi Sun
2024-11-04 3:45 ` [PATCH v3 3/5] f2fs: introduce update_sit_entry_for_release() Yi Sun
2024-12-20 21:22 ` Jaegeuk Kim [this message]
2024-11-04 3:45 ` [PATCH v3 4/5] f2fs: add parameter @len to f2fs_invalidate_blocks() Yi Sun
2024-11-04 3:45 ` [PATCH v3 5/5] f2fs: Optimize f2fs_truncate_data_blocks_range() Yi Sun
2024-12-11 3:08 ` yi sun
2024-12-12 16:22 ` Jaegeuk Kim
2024-12-18 8:00 ` yi sun
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=Z2XgAMRm6uMAT2XM@google.com \
--to=jaegeuk@kernel.org \
--cc=Hao_hao.Wang@unisoc.com \
--cc=chao@kernel.org \
--cc=ke.wang@unisoc.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=niuzhiguo84@gmail.com \
--cc=sunyibuaa@gmail.com \
--cc=yi.sun@unisoc.com \
/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