Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Subject: Re: [f2fs-dev] [PATCH] f2fs: introduce sysfs/data_io_flag to attach
 REQ_META/FUA
To:     Jaegeuk Kim <jaegeuk@kernel.org>
CC:     <linux-kernel@vger.kernel.org>,
        <linux-f2fs-devel@lists.sourceforge.net>, <kernel-team@android.com>
References: <20200403161249.68385-1-jaegeuk@kernel.org>
 <0e627c29-7fb0-5bd6-c1d9-b96a94df62ae@huawei.com>
 <20200407025913.GB137081@google.com>
From:   Chao Yu <yuchao0@huawei.com>
Message-ID: <2ca452cd-073a-29fa-1884-99ad1199bb97@huawei.com>
Date:   Tue, 7 Apr 2020 11:40:51 +0800
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <20200407025913.GB137081@google.com>
Content-Type: text/plain; charset="windows-1252"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On 2020/4/7 10:59, Jaegeuk Kim wrote:
> On 04/07, Chao Yu wrote:
>> On 2020/4/4 0:12, Jaegeuk Kim wrote:
>>> This patch introduces a way to attach REQ_META/FUA explicitly
>>> to all the data writes given temperature.
>>>
>>> -> attach REQ_FUA to Hot Data writes
>>>
>>> -> attach REQ_FUA to Hot|Warm Data writes
>>>
>>> -> attach REQ_FUA to Hot|Warm|Cold Data writes
>>>
>>> -> attach REQ_FUA to Hot|Warm|Cold Data writes as well as
>>>           REQ_META to Hot Data writes
>>
>> Out of curiosity, what scenario it is used for?
> 
> It's testing purpose to compare the bandwidths per different IO flags.

Thanks for the hint. :)

As nobarrier was set in Android, so REQ_PREFLUSH will not be considered in
this sysfs interface?

Thanks,

> 
>>
>> Thanks,
> .
>