From: Chao Yu <yuchao0@huawei.com>
To: sunqiuyang <sunqiuyang@huawei.com>,
<linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<linux-f2fs-devel@lists.sourceforge.net>
Cc: Sahitya Tummala <stummala@codeaurora.org>
Subject: Re: [PATCH v6 1/1] f2fs: ioctl for removing a range from F2FS
Date: Fri, 24 May 2019 10:32:07 +0800 [thread overview]
Message-ID: <e7cfed52-0212-834f-aed8-0c5abc07f779@huawei.com> (raw)
In-Reply-To: <20190524015555.12622-1-sunqiuyang@huawei.com>
+Cc Sahitya,
On 2019/5/24 9:55, sunqiuyang wrote:
> From: Qiuyang Sun <sunqiuyang@huawei.com>
>
> This ioctl shrinks a given length (aligned to sections) from end of the
> main area. Any cursegs and valid blocks will be moved out before
> invalidating the range.
>
> This feature can be used for adjusting partition sizes online.
> --
> Changlog v1 ==> v2:
>
> Sahitya Tummala:
> - Add this ioctl for f2fs_compat_ioctl() as well.
> - Fix debugfs status to reflect the online resize changes.
> - Fix potential race between online resize path and allocate new data
> block path or gc path.
>
> Others:
> - Rename some identifiers.
> - Add some error handling branches.
> - Clear sbi->next_victim_seg[BG_GC/FG_GC] in shrinking range.
> --
> Changelog v2 ==> v3:
> Implement this interface as ext4's, and change the parameter from shrunk
> bytes to new block count of F2FS.
> --
> Changelog v3 ==> v4:
> - During resizing, force to empty sit_journal and forbid adding new
> entries to it, in order to avoid invalid segno in journal after resize.
> - Reduce sbi->user_block_count before resize starts.
> - Commit the updated superblock first, and then update in-memory metadata
> only when the former succeeds.
> - Target block count must align to sections.
> --
> Changelog v4 ==> v5:
> Write checkpoint before and after committing the new superblock, w/o
> CP_FSCK_FLAG respectively, so that the FS can be fixed by fsck even if
> resize fails after the new superblock is committed.
> --
> Changelog v5 ==> v6:
> - In free_segment_range(), reduce granularity of gc_mutex.
> - Add protection on curseg migration.
>
> Signed-off-by: Qiuyang Sun <sunqiuyang@huawei.com>
> Signed-off-by: Chao Yu <yuchao0@huawei.com>
> Signed-off-by: Sahitya Tummala <stummala@codeaurora.org>
Looks good to me now,
Reviewed-by: Chao Yu <yuchao0@huawei.com>
To Sahitya, is it okay to you merging all your fixes and adding Signed-off in
original patch? We can still separate them from this patch if you object this,
let us know.
Thanks,
next prev parent reply other threads:[~2019-05-24 2:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-24 1:55 sunqiuyang
2019-05-24 2:32 ` Chao Yu [this message]
2019-05-24 3:09 ` Sahitya Tummala
2019-05-24 3:28 ` Chao Yu
2019-05-30 16:06 ` Jaegeuk Kim
2019-05-31 1:48 ` Chao Yu
2019-06-03 16:23 ` Jaegeuk Kim
2019-06-04 1:43 ` Chao Yu
2019-06-04 10:25 ` sunqiuyang
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=e7cfed52-0212-834f-aed8-0c5abc07f779@huawei.com \
--to=yuchao0@huawei.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stummala@codeaurora.org \
--cc=sunqiuyang@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
all inboxes | Powered by JetHome®