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;
Date:   Mon, 6 Apr 2020 19:59:13 -0700
From:   Jaegeuk Kim <jaegeuk@kernel.org>
To:     Chao Yu <yuchao0@huawei.com>
Cc:     linux-kernel@vger.kernel.org,
        linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com
Subject: Re: [f2fs-dev] [PATCH] f2fs: introduce sysfs/data_io_flag to attach
 REQ_META/FUA
Message-ID: <20200407025913.GB137081@google.com>
References: <20200403161249.68385-1-jaegeuk@kernel.org>
 <0e627c29-7fb0-5bd6-c1d9-b96a94df62ae@huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <0e627c29-7fb0-5bd6-c1d9-b96a94df62ae@huawei.com>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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,