From: Chao Yu <chao@kernel.org>
To: Daeho Jeong <daeho43@gmail.com>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com
Cc: Daeho Jeong <daehojeong@google.com>
Subject: Re: [f2fs-dev] [PATCH v5] f2fs: introduce fragment allocation mode mount option
Date: Thu, 21 Oct 2021 19:29:33 +0800 [thread overview]
Message-ID: <0e77ea3e-196e-cc41-91eb-abc89ca6d522@kernel.org> (raw)
In-Reply-To: <20210929181203.1606675-1-daeho43@gmail.com>
On 2021/9/30 2:12, Daeho Jeong wrote:
> From: Daeho Jeong <daehojeong@google.com>
>
> Added two options into "mode=" mount option to make it possible for
> developers to simulate filesystem fragmentation/after-GC situation
> itself. The developers use these modes to understand filesystem
> fragmentation/after-GC condition well, and eventually get some
> insights to handle them better.
>
> "fragment:segment": f2fs allocates a new segment in ramdom position.
> With this, we can simulate the after-GC condition.
> "fragment:block" : We can scatter block allocation with
> "max_fragment_chunk" and "max_fragment_hole" sysfs
> nodes. f2fs will allocate 1..<max_fragment_chunk>
> blocks in a chunk and make a hole in the length of
> 1..<max_fragment_hole> by turns in a newly allocated
> free segment. Plus, this mode implicitly enables
> "fragment:segment" option for more randomness.
>
> Signed-off-by: Daeho Jeong <daehojeong@google.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2021-10-21 11:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-29 18:12 [f2fs-dev] [PATCH v5] f2fs: introduce fragment allocation mode mount option Daeho Jeong
2021-10-21 11:29 ` Chao Yu [this message]
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=0e77ea3e-196e-cc41-91eb-abc89ca6d522@kernel.org \
--to=chao@kernel.org \
--cc=daeho43@gmail.com \
--cc=daehojeong@google.com \
--cc=kernel-team@android.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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).