Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Subject: Re: [f2fs-dev] [PATCH v3] f2fs: introduce fragment allocation mode
 mount option
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>
References: <20210831051037.3108944-1-daeho43@gmail.com>
 <33e7e327-5318-e30f-4419-42497fe90b31@kernel.org>
 <CACOAw_wyLX_mnnPV0vWeAqTtEDx_bhG2c72jq6YmjQGOgtVLeg@mail.gmail.com>
From:   Chao Yu <chao@kernel.org>
Message-ID: <04c6fb07-0e56-bfda-44b2-8fcb4a9fe72a@kernel.org>
Date:   Thu, 2 Sep 2021 22:14:33 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.13.0
MIME-Version: 1.0
In-Reply-To: <CACOAw_wyLX_mnnPV0vWeAqTtEDx_bhG2c72jq6YmjQGOgtVLeg@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Precedence: bulk

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?

>