From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
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
Date: Tue, 7 Apr 2020 11:40:51 +0800 [thread overview]
Message-ID: <2ca452cd-073a-29fa-1884-99ad1199bb97@huawei.com> (raw)
In-Reply-To: <20200407025913.GB137081@google.com>
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,
> .
>
next prev parent reply other threads:[~2020-04-07 3:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 16:12 [PATCH] f2fs: introduce sysfs/data_io_flag to attach REQ_META/FUA Jaegeuk Kim
2020-04-07 2:16 ` [f2fs-dev] " Chao Yu
2020-04-07 2:59 ` Jaegeuk Kim
2020-04-07 3:40 ` Chao Yu [this message]
2020-04-09 2:20 ` Jaegeuk Kim
2020-04-09 2:23 ` Chao Yu
2020-04-09 2:28 ` Jaegeuk Kim
2020-04-09 2:31 ` Chao Yu
2020-04-16 7:18 ` Chao Yu
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=2ca452cd-073a-29fa-1884-99ad1199bb97@huawei.com \
--to=yuchao0@huawei.com \
--cc=jaegeuk@kernel.org \
--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).