From: Yunlong Song <yunlong.song@huawei.com>
To: Chao Yu <yuchao0@huawei.com>, Jaegeuk Kim <jaegeuk@kernel.org>
Cc: chao@kernel.org, sylinux@163.com, miaoxie@huawei.com,
bintian.wang@huawei.com, linux-fsdevel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] f2fs: provide more chance for node and data to get ssr segment
Date: Fri, 24 Feb 2017 17:19:13 +0800 [thread overview]
Message-ID: <58AFFA91.2030904@huawei.com> (raw)
In-Reply-To: <3d4b064b-817f-402f-3eb5-df3ec7c06b44@huawei.com>
Hi Jaegeuk and Chao,
How about the question I pointed out in last mail:
Why not take "neighboring temperature" for ssr? For example, if type == CURSEG_COLD_DATA,
the new patch selects CURSEG_HOT_DATA first, why not select CURSEG_WARM_DATA first?
The patch I sent ensure this "neighboring temperature" for ssr. This is to reduce the influence of
mixing different levels of hot/code node types.
On 2017/2/24 17:05, Chao Yu wrote:
> Hi Jaegeuk,
>
> Reviewed-by: Chao Yu <yuchao0@huawei.com>
>
> For your attached two patches.
>
> Thanks,
>
> On 2017/2/23 9:17, Jaegeuk Kim wrote:
>> Hi Yunlong,
>>
>> I've been testing the similar patches as I attached.
>>
>> Thanks,
>>
>> On 02/22, Yunlong Song wrote:
>>> Signed-off-by: Yunlong Song <yunlong.song@huawei.com>
>>> ---
>>> fs/f2fs/segment.c | 9 +++++++++
>>> 1 file changed, 9 insertions(+)
>>>
>>> diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
>>> index 9d13743..5fe71b9 100644
>>> --- a/fs/f2fs/segment.c
>>> +++ b/fs/f2fs/segment.c
>>> @@ -1540,12 +1540,17 @@ static int get_ssr_segment(struct f2fs_sb_info *sbi, int type)
>>> {
>>> struct curseg_info *curseg = CURSEG_I(sbi, type);
>>> const struct victim_selection *v_ops = DIRTY_I(sbi)->v_ops;
>>> + int old_type = type;
>>>
>>> if (IS_NODESEG(type)) {
>>> for (; type >= CURSEG_HOT_NODE; type--)
>>> if (v_ops->get_victim(sbi, &(curseg)->next_segno,
>>> BG_GC, type, SSR))
>>> return 1;
>>> + for (type = old_type + 1; type <= CURSEG_COLD_NODE; type++)
>>> + if (v_ops->get_victim(sbi, &(curseg)->next_segno,
>>> + BG_GC, type, SSR))
>>> + return 1;
>>> return 0;
>>> }
>>>
>>> @@ -1554,6 +1559,10 @@ static int get_ssr_segment(struct f2fs_sb_info *sbi, int type)
>>> if (v_ops->get_victim(sbi, &(curseg)->next_segno,
>>> BG_GC, type, SSR))
>>> return 1;
>>> + for (type = old_type + 1; type <= CURSEG_COLD_DATA; type++)
>>> + if (v_ops->get_victim(sbi, &(curseg)->next_segno,
>>> + BG_GC, type, SSR))
>>> + return 1;
>>> return 0;
>>> }
>>>
>>> --
>>> 1.8.5.2
>
> .
>
--
Thanks,
Yunlong Song
WARNING: multiple messages have this Message-ID (diff)
From: Yunlong Song <yunlong.song@huawei.com>
To: Chao Yu <yuchao0@huawei.com>, Jaegeuk Kim <jaegeuk@kernel.org>
Cc: <chao@kernel.org>, <sylinux@163.com>, <miaoxie@huawei.com>,
<bintian.wang@huawei.com>, <linux-fsdevel@vger.kernel.org>,
<linux-f2fs-devel@lists.sourceforge.net>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] f2fs: provide more chance for node and data to get ssr segment
Date: Fri, 24 Feb 2017 17:19:13 +0800 [thread overview]
Message-ID: <58AFFA91.2030904@huawei.com> (raw)
In-Reply-To: <3d4b064b-817f-402f-3eb5-df3ec7c06b44@huawei.com>
Hi Jaegeuk and Chao,
How about the question I pointed out in last mail:
Why not take "neighboring temperature" for ssr? For example, if type == CURSEG_COLD_DATA,
the new patch selects CURSEG_HOT_DATA first, why not select CURSEG_WARM_DATA first?
The patch I sent ensure this "neighboring temperature" for ssr. This is to reduce the influence of
mixing different levels of hot/code node types.
On 2017/2/24 17:05, Chao Yu wrote:
> Hi Jaegeuk,
>
> Reviewed-by: Chao Yu <yuchao0@huawei.com>
>
> For your attached two patches.
>
> Thanks,
>
> On 2017/2/23 9:17, Jaegeuk Kim wrote:
>> Hi Yunlong,
>>
>> I've been testing the similar patches as I attached.
>>
>> Thanks,
>>
>> On 02/22, Yunlong Song wrote:
>>> Signed-off-by: Yunlong Song <yunlong.song@huawei.com>
>>> ---
>>> fs/f2fs/segment.c | 9 +++++++++
>>> 1 file changed, 9 insertions(+)
>>>
>>> diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
>>> index 9d13743..5fe71b9 100644
>>> --- a/fs/f2fs/segment.c
>>> +++ b/fs/f2fs/segment.c
>>> @@ -1540,12 +1540,17 @@ static int get_ssr_segment(struct f2fs_sb_info *sbi, int type)
>>> {
>>> struct curseg_info *curseg = CURSEG_I(sbi, type);
>>> const struct victim_selection *v_ops = DIRTY_I(sbi)->v_ops;
>>> + int old_type = type;
>>>
>>> if (IS_NODESEG(type)) {
>>> for (; type >= CURSEG_HOT_NODE; type--)
>>> if (v_ops->get_victim(sbi, &(curseg)->next_segno,
>>> BG_GC, type, SSR))
>>> return 1;
>>> + for (type = old_type + 1; type <= CURSEG_COLD_NODE; type++)
>>> + if (v_ops->get_victim(sbi, &(curseg)->next_segno,
>>> + BG_GC, type, SSR))
>>> + return 1;
>>> return 0;
>>> }
>>>
>>> @@ -1554,6 +1559,10 @@ static int get_ssr_segment(struct f2fs_sb_info *sbi, int type)
>>> if (v_ops->get_victim(sbi, &(curseg)->next_segno,
>>> BG_GC, type, SSR))
>>> return 1;
>>> + for (type = old_type + 1; type <= CURSEG_COLD_DATA; type++)
>>> + if (v_ops->get_victim(sbi, &(curseg)->next_segno,
>>> + BG_GC, type, SSR))
>>> + return 1;
>>> return 0;
>>> }
>>>
>>> --
>>> 1.8.5.2
>
> .
>
--
Thanks,
Yunlong Song
next prev parent reply other threads:[~2017-02-24 9:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 12:50 [PATCH 1/3] f2fs: clean up codes in get_ssr_segment Yunlong Song
2017-02-22 12:50 ` Yunlong Song
2017-02-22 12:50 ` [PATCH 2/3] f2fs: provide more chance to get node ssr Yunlong Song
2017-02-22 12:50 ` Yunlong Song
2017-02-22 12:50 ` [PATCH 3/3] f2fs: provide more chance for node and data to get ssr segment Yunlong Song
2017-02-22 12:50 ` Yunlong Song
2017-02-23 1:17 ` Jaegeuk Kim
2017-02-23 2:13 ` Yunlong Song
2017-02-23 2:13 ` Yunlong Song
2017-02-23 2:41 ` Yunlong Song
2017-02-23 2:41 ` Yunlong Song
2017-02-24 9:05 ` Chao Yu
2017-02-24 9:05 ` Chao Yu
2017-02-24 9:19 ` Yunlong Song [this message]
2017-02-24 9:19 ` Yunlong Song
2017-02-24 10:47 ` Chao Yu
2017-02-24 10:47 ` Chao Yu
2017-02-24 11:41 ` Yunlong Song
2017-02-24 11:41 ` Yunlong Song
2017-02-24 17:58 ` Jaegeuk Kim
[not found] ` <b5c6b4d.d7.15a7177d92d.Coremail.sylinux@163.com>
2017-02-24 20:05 ` Jaegeuk Kim
2017-02-24 20:05 ` Jaegeuk Kim
2017-02-25 2:16 ` Yunlong Song
2017-02-25 2:16 ` Yunlong Song
2017-02-23 0:41 ` [PATCH 1/3] f2fs: clean up codes in get_ssr_segment Jaegeuk Kim
2017-02-23 0:59 ` Jaegeuk Kim
2017-02-23 1:55 ` Yunlong Song
2017-02-23 1:55 ` Yunlong Song
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=58AFFA91.2030904@huawei.com \
--to=yunlong.song@huawei.com \
--cc=bintian.wang@huawei.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miaoxie@huawei.com \
--cc=sylinux@163.com \
--cc=yuchao0@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.