From: Chao Yu <yuchao0@huawei.com>
To: <daejun7.park@samsung.com>,
"jaegeuk@kernel.org" <jaegeuk@kernel.org>,
"chao@kernel.org" <chao@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-f2fs-devel@lists.sourceforge.net"
<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [PATCH] f2fs: set file as cold when file defragmentation
Date: Thu, 6 May 2021 10:09:18 +0800 [thread overview]
Message-ID: <3a0ab201-9546-d523-abc7-79df5f637f14@huawei.com> (raw)
In-Reply-To: <20210429062005epcms2p352ef77f96ab66cbffe0c0ab6c1b62d8a@epcms2p3>
On 2021/4/29 14:20, Daejun Park wrote:
> In file defragmentation by ioctl, all data blocks in the file are
> re-written out-of-place. File defragmentation implies user will not update
> and mostly read the file. So before the defragmentation, we set file
> temperature as cold for better block allocation.
I don't think all fragmented files are cold, e.g. db file.
We have separated interface (via f2fs_xattr_advise_handler, e.g. setfattr -n
"system.advise" -v value) to indicate this file is a hot/cold file, so my
suggestion is after file defragmentation, if you think this file is cold, and
use setxattr() to set it as cold.
Thanks,
>
> Signed-off-by: Daejun Park <daejun7.park@samsung.com>
> ---
> fs/f2fs/file.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/fs/f2fs/file.c b/fs/f2fs/file.c
> index d697c8900fa7..dcac965a05fe 100644
> --- a/fs/f2fs/file.c
> +++ b/fs/f2fs/file.c
> @@ -2669,6 +2669,9 @@ static int f2fs_defragment_range(struct f2fs_sb_info *sbi,
> map.m_len = pg_end - pg_start;
> total = 0;
>
> + if (!file_is_cold(inode))
> + file_set_cold(inode);
> +
> while (map.m_lblk < pg_end) {
> pgoff_t idx;
> int cnt = 0;
>
next prev parent reply other threads:[~2021-05-06 2:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210429062005epcms2p352ef77f96ab66cbffe0c0ab6c1b62d8a@epcms2p3>
2021-04-29 6:20 ` [PATCH] f2fs: set file as cold when file defragmentation Daejun Park
2021-05-06 2:09 ` Chao Yu [this message]
2021-05-06 4:46 ` Jaegeuk Kim
2021-05-06 6:36 ` Chao Yu
2021-05-10 14:47 ` Jaegeuk Kim
2021-05-11 1:30 ` Chao Yu
2021-05-11 5:09 ` Jaegeuk Kim
2021-05-11 6:07 ` Chao Yu
[not found] ` <CGME20210429062005epcms2p352ef77f96ab66cbffe0c0ab6c1b62d8a@epcms2p1>
2021-05-11 6:41 ` Daejun Park
2021-05-11 7:23 ` Chao Yu
2021-05-11 21:47 ` Jaegeuk Kim
[not found] ` <CGME20210429062005epcms2p352ef77f96ab66cbffe0c0ab6c1b62d8a@epcms2p6>
2021-05-12 8:45 ` 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=3a0ab201-9546-d523-abc7-79df5f637f14@huawei.com \
--to=yuchao0@huawei.com \
--cc=chao@kernel.org \
--cc=daejun7.park@samsung.com \
--cc=jaegeuk@kernel.org \
--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).