From: Chao Yu <yuchao0@huawei.com>
To: Hyunchul Lee <hyc.lee@gmail.com>, Jaegeuk Kim <jaegeuk@kernel.org>
Cc: <linux-f2fs-devel@lists.sourceforge.net>,
<linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
<kernel-team@lge.com>, Jens Axboe <axboe@kernel.dk>,
Hyunchul Lee <cheol.lee@lge.com>
Subject: Re: [PATCH 1/2] f2fs: pass down write hints to block layer for bufferd write
Date: Thu, 30 Nov 2017 15:06:25 +0800 [thread overview]
Message-ID: <d71418e1-d667-3dc6-9265-61db5d8f40bc@huawei.com> (raw)
In-Reply-To: <1511828607-624-1-git-send-email-hyc.lee@gmail.com>
Hi Hyunchul,
On 2017/11/28 8:23, Hyunchul Lee wrote:
> From: Hyunchul Lee <cheol.lee@lge.com>
>
> This implements which hint is passed down to block layer
> for datas from the specific segment type.
>
> segment type hints
> ------------ -----
> COLD_NODE & COLD_DATA WRITE_LIFE_EXTREME
> WARM_DATA WRITE_LIFE_NONE
> HOT_NODE & WARM_NODE WRITE_LIFE_LONG
> HOT_DATA WRITE_LIFE_MEDIUM
> META_DATA WRITE_LIFE_SHORT
Just noticed, if our user do not give the hint via ioctl, f2fs can
provider hint to lower layer according to hot/cold separation ability,
it will be okay. But once user give his hint which may be more accurate
than filesystem, hint converted by f2fs may be wrong.
So what do you think of adding an option to control whether filesystem
can convert hint user given?
Thanks,
next prev parent reply other threads:[~2017-11-30 7:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 0:23 Hyunchul Lee
2017-11-28 0:23 ` [PATCH 2/2] f2fs: pass down write hints to block layer for direct write Hyunchul Lee
2017-11-30 6:32 ` [PATCH 1/2] f2fs: pass down write hints to block layer for bufferd write Chao Yu
2017-12-01 7:28 ` Jaegeuk Kim
2017-12-01 8:50 ` Hyunchul Lee
2017-12-14 21:18 ` Jaegeuk Kim
2017-11-30 7:06 ` Chao Yu [this message]
2017-12-01 8:28 ` Hyunchul Lee
2017-12-11 13:15 ` [f2fs-dev] " Chao Yu
2017-12-12 2:15 ` Hyunchul Lee
2017-12-12 2:45 ` Chao Yu
2017-12-14 1:33 ` Hyunchul Lee
2017-12-15 2:06 ` Jaegeuk Kim
2017-12-18 7:28 ` Hyunchul Lee
2017-12-23 9:44 ` Chao Yu
2017-12-28 3:26 ` Jaegeuk Kim
2017-12-28 5:05 ` Hyunchul Lee
2017-12-28 16:32 ` Jaegeuk Kim
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=d71418e1-d667-3dc6-9265-61db5d8f40bc@huawei.com \
--to=yuchao0@huawei.com \
--cc=axboe@kernel.dk \
--cc=cheol.lee@lge.com \
--cc=hyc.lee@gmail.com \
--cc=jaegeuk@kernel.org \
--cc=kernel-team@lge.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--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
Powered by JetHome