From: Chao Yu <yuchao0@huawei.com>
To: <daejun7.park@samsung.com>,
"jaegeuk@kernel.org" <jaegeuk@kernel.org>,
"chao@kernel.org" <chao@kernel.org>
Cc: yongmyung lee <ymhungry.lee@samsung.com>,
Jieon Seol <jieon.seol@samsung.com>,
Sang-yoon Oh <sangyoon.oh@samsung.com>,
Mankyu PARK <manq.park@samsung.com>,
Sung-Jun Park <sungjun07.park@samsung.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-f2fs-devel@lists.sourceforge.net"
<linux-f2fs-devel@lists.sourceforge.net>,
Keoseong Park <keosung.park@samsung.com>,
SEUNGUK SHIN <seunguk.shin@samsung.com>,
"Jinyoung CHOI" <j-young.choi@samsung.com>,
Jaemyung Lee <jaemyung.lee@samsung.com>
Subject: Re: [f2fs-dev] [PATCH] f2fs: change write_hint for hot/warm nodes
Date: Tue, 3 Nov 2020 16:28:49 +0800 [thread overview]
Message-ID: <609445f8-de3b-eb79-449c-020125799449@huawei.com> (raw)
In-Reply-To: <20201103064039epcms2p30ecac0e7cefff0d50745f2e2e61ce38e@epcms2p3>
On 2020/11/3 14:40, Daejun Park wrote:
>>From 818a76a9aee5bf225565264274d211edb07bae7d Mon Sep 17 00:00:00 2001
> From: Daejun Park <daejun7.park@samsung.com>
> Date: Tue, 3 Nov 2020 15:30:26 +0900
>
>
> In the fs-based mode of F2FS, the mapping of hot/warm node to
> WRITE_LIFE_NOT_SET should be changed to WRITE_LIFE_SHORT.
>
> As a result of analyzing the write pattern of f2fs using real workload,
> hot/warm nodes have high update ratio close to hot data.[*]
> However, F2FS passes write hints for hot/warm nodes as WRITE_LIFE_NOT_SET.
>
> Furthermore, WRITE_LIFE_NOT_SET is a default value of write hint when it is
> not provided from the file system.
> In storage, write_hint is used to distinguish streams (e.g. NVMe).
> So, the hot/warm node of F2FS is not distinguished from other write_hints,
> which can make the wrong stream seperation.
>
> * Liang, Yu, et al. "An empirical study of F2FS on mobile devices." 2017
> IEEE 23rd International Conference on Embedded and Real-Time Computing
> Systems and Applications (RTCSA).
Could you please update Documentation/filesystems/f2fs.rst as well?
Thanks,
>
> Signed-off-by: Daejun Park <daejun7.park@samsung.com>
> ---
> fs/f2fs/segment.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
> index 1596502f7375..7b42bb10c6c3 100644
> --- a/fs/f2fs/segment.c
> +++ b/fs/f2fs/segment.c
> @@ -3208,7 +3208,7 @@ enum rw_hint f2fs_io_type_to_rw_hint(struct f2fs_sb_info *sbi,
> return WRITE_LIFE_EXTREME;
> } else if (type == NODE) {
> if (temp == WARM || temp == HOT)
> - return WRITE_LIFE_NOT_SET;
> + return WRITE_LIFE_SHORT;
> else if (temp == COLD)
> return WRITE_LIFE_NONE;
> } else if (type == META) {
>
next prev parent reply other threads:[~2020-11-03 8:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20201103064039epcms2p30ecac0e7cefff0d50745f2e2e61ce38e@epcms2p3>
2020-11-03 6:40 ` Daejun Park
2020-11-03 8:28 ` Chao Yu [this message]
[not found] ` <CGME20201103064039epcms2p30ecac0e7cefff0d50745f2e2e61ce38e@epcms2p8>
2020-11-03 8:33 ` Daejun Park
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=609445f8-de3b-eb79-449c-020125799449@huawei.com \
--to=yuchao0@huawei.com \
--cc=chao@kernel.org \
--cc=daejun7.park@samsung.com \
--cc=j-young.choi@samsung.com \
--cc=jaegeuk@kernel.org \
--cc=jaemyung.lee@samsung.com \
--cc=jieon.seol@samsung.com \
--cc=keosung.park@samsung.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=manq.park@samsung.com \
--cc=sangyoon.oh@samsung.com \
--cc=seunguk.shin@samsung.com \
--cc=sungjun07.park@samsung.com \
--cc=ymhungry.lee@samsung.com \
/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®