From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Junling Zheng <zhengjunling@huawei.com>
Cc: linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [PATCH] mkfs.f2fs: recalculate sit_segments by max_sit_bitmap_size
Date: Mon, 22 Feb 2016 09:31:46 -0800 [thread overview]
Message-ID: <20160222173146.GA10875@jaegeuk.gateway> (raw)
In-Reply-To: <1455785944-19687-1-git-send-email-zhengjunling@huawei.com>
Hi Junling,
On Thu, Feb 18, 2016 at 04:59:04PM +0800, Junling Zheng wrote:
> In most cases, sit_bitmap_size is smaller than MAX_SIT_BITMAP_SIZE.
>
> However, in some extreme scenarios, such as 16TB, sit_bitmap_size
> could be larger than MAX_SIT_BITMAP_SIZE.
>
> In this case, we should recalculate the sit_segments through
> max_sit_bitmap_size to prevent sit_ver_bitmap_bytesize got from
> segment_count_sit in f2fs_write_check_point_pack() being over
> MAX_SIT_BITMAP_SIZE.
>
> Signed-off-by: Junling Zheng <zhengjunling@huawei.com>
> ---
> mkfs/f2fs_format.c | 24 +++++++++++++++++-------
> 1 file changed, 17 insertions(+), 7 deletions(-)
>
> diff --git a/mkfs/f2fs_format.c b/mkfs/f2fs_format.c
> index 645c2aa..24b2cc1 100644
> --- a/mkfs/f2fs_format.c
> +++ b/mkfs/f2fs_format.c
> @@ -191,6 +191,23 @@ static int f2fs_prepare_super_block(void)
>
> sit_segments = SEG_ALIGN(blocks_for_sit);
>
> + /*
> + * In most cases, sit_bitmap_size is smaller than MAX_SIT_BITMAP_SIZE.
> + * However, in an extreme scenario(16TB), sit_bitmap_size could be larger
> + * than MAX_SIT_BITMAP_SIZE. Thus, we should recalculate the sit_segments
> + * to prevent sit_ver_bitmap_bytesize got from segment_count_sit in
> + * f2fs_write_check_point_pack() being over MAX_SIT_BITMAP_SIZE.
> + */
> + sit_bitmap_size = (sit_segments << log_blks_per_seg) / 8;
> +
> + if (sit_bitmap_size > MAX_SIT_BITMAP_SIZE) {
> + max_sit_bitmap_size = MAX_SIT_BITMAP_SIZE;
> + sit_segments = max_sit_bitmap_size * 8 >> log_blks_per_seg;
> + blocks_for_sit = sit_segments << log_blks_per_seg;
> + }
> + else
> + max_sit_bitmap_size = sit_bitmap_size;
Codling style.
if {
} else {
}
Anyway, what about just redefining MAX_SIT_BITMAP_SIZE as
(ALIGN(F2FS_MAX_SEGMENT, SIT_ENTRY_PER_BLOCK) / 8) ?
Thanks,
> +
> set_sb(segment_count_sit, sit_segments * 2);
>
> set_sb(nat_blkaddr, get_sb(sit_blkaddr) + get_sb(segment_count_sit) *
> @@ -208,13 +225,6 @@ static int f2fs_prepare_super_block(void)
> * This number resizes NAT bitmap area in a CP page.
> * So the threshold is determined not to overflow one CP page
> */
> - sit_bitmap_size = ((get_sb(segment_count_sit) / 2) <<
> - log_blks_per_seg) / 8;
> -
> - if (sit_bitmap_size > MAX_SIT_BITMAP_SIZE)
> - max_sit_bitmap_size = MAX_SIT_BITMAP_SIZE;
> - else
> - max_sit_bitmap_size = sit_bitmap_size;
>
> /*
> * It should be reserved minimum 1 segment for nat.
> --
> 1.9.1
>
>
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
> _______________________________________________
> Linux-f2fs-devel mailing list
> Linux-f2fs-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
next prev parent reply other threads:[~2016-02-22 17:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-18 8:59 [PATCH] mkfs.f2fs: recalculate sit_segments by max_sit_bitmap_size Junling Zheng
2016-02-22 17:31 ` Jaegeuk Kim [this message]
2016-02-23 3:33 ` Junling Zheng
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=20160222173146.GA10875@jaegeuk.gateway \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=zhengjunling@huawei.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;
as well as URLs for NNTP newsgroup(s).