All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yunlong Song <yunlong.song@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: cm224.lee@samsung.com, yuchao0@huawei.com, 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: Thu, 23 Feb 2017 10:41:21 +0800	[thread overview]
Message-ID: <58AE4BD1.90301@huawei.com> (raw)
In-Reply-To: <58AE452D.60500@huawei.com>

Hi Jay,
    I miss some codes from your mail, now I check all your patch codes and make clear with question 2 and 3, it's fine.

    But still, how about question 1?

On 2017/2/23 10:13, Yunlong Song wrote:
> Hi Jay,
>     But there are some differences:
> 1 Why not take "neighboring temperature" for ssr? For example, if type == CURSEG_COLD_DATA,
>     your new patch selects CURSEG_HOT_DATA first, how about select CURSEG_WARM_DATA first?
>     The patch I sent ensure this "neighboring temperature" for ssr.
> 2 Your new patch returns 0 for node ssr, does get_ssr_segment work only for data?
> 3 I see your new patch just "continue" when i == type, why not consider the current type?
>
> 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: Jaegeuk Kim <jaegeuk@kernel.org>
Cc: <cm224.lee@samsung.com>, <yuchao0@huawei.com>, <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: Thu, 23 Feb 2017 10:41:21 +0800	[thread overview]
Message-ID: <58AE4BD1.90301@huawei.com> (raw)
In-Reply-To: <58AE452D.60500@huawei.com>

Hi Jay,
    I miss some codes from your mail, now I check all your patch codes and make clear with question 2 and 3, it's fine.

    But still, how about question 1?

On 2017/2/23 10:13, Yunlong Song wrote:
> Hi Jay,
>     But there are some differences:
> 1 Why not take "neighboring temperature" for ssr? For example, if type == CURSEG_COLD_DATA,
>     your new patch selects CURSEG_HOT_DATA first, how about select CURSEG_WARM_DATA first?
>     The patch I sent ensure this "neighboring temperature" for ssr.
> 2 Your new patch returns 0 for node ssr, does get_ssr_segment work only for data?
> 3 I see your new patch just "continue" when i == type, why not consider the current type?
>
> 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

  reply	other threads:[~2017-02-23  2:41 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 [this message]
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
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=58AE4BD1.90301@huawei.com \
    --to=yunlong.song@huawei.com \
    --cc=bintian.wang@huawei.com \
    --cc=chao@kernel.org \
    --cc=cm224.lee@samsung.com \
    --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.