From: Chao Yu <chao@kernel.org>
To: Daeho Jeong <daeho43@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com,
Daeho Jeong <daehojeong@google.com>
Subject: Re: [f2fs-dev] [PATCH v3] f2fs: introduce fragment allocation mode mount option
Date: Thu, 2 Sep 2021 22:14:33 +0800 [thread overview]
Message-ID: <04c6fb07-0e56-bfda-44b2-8fcb4a9fe72a@kernel.org> (raw)
In-Reply-To: <CACOAw_wyLX_mnnPV0vWeAqTtEDx_bhG2c72jq6YmjQGOgtVLeg@mail.gmail.com>
On 2021/9/1 23:17, Daeho Jeong wrote:
>>
>> if (F2FS_OPTION(sbi).fs_mode == FS_MODE_FRAGMENT_SEG)?
>>
>> It needs to randomize position of next segment only in fragment_seg mode? IIRC.
>>
>
> I want the randomness of segment allocation in fragment:*_block mode
> to simulate real filesystem fragmentation.
> How about just using fragment:rand_block for the simulation. I mean we
> can use segment randomness for fragment:segment and
> fragment:rand_block.
Okay, so it needs to describe that fragment:rand_block option has implicitly
enables fragment:segment option in document?
>
prev parent reply other threads:[~2021-09-02 14:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-31 5:10 Daeho Jeong
2021-09-01 6:58 ` [f2fs-dev] " Chao Yu
2021-09-01 15:17 ` Daeho Jeong
2021-09-02 14:14 ` 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=04c6fb07-0e56-bfda-44b2-8fcb4a9fe72a@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
all inboxes | Powered by JetHome®