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 1/3] f2fs: clean up codes in get_ssr_segment
Date: Thu, 23 Feb 2017 09:55:29 +0800 [thread overview]
Message-ID: <58AE4111.2070406@huawei.com> (raw)
In-Reply-To: <20170223005915.GG4003@jaegeuk.local>
Yes, exactly, I just mean it for short with word "clean up", thanks for correction.
On 2017/2/23 8:59, Jaegeuk Kim wrote:
> On 02/22, Jaegeuk Kim wrote:
>> Hi Yunlong,
>>
>> This is NOT clean-up. What's your point here?
> I guess you wanted to do like this.
>
> >From 8d344ac45890dd95c5734fd29a19a7c19364c327 Mon Sep 17 00:00:00 2001
> From: Yunlong Song <yunlong.song@huawei.com>
> Date: Wed, 22 Feb 2017 20:50:49 +0800
> Subject: [PATCH] f2fs: do SSR for data when there is enough free space
>
> In allocate_segment_by_default(), need_SSR() already detected it's time to do
> SSR. So, let's try to find victims for data segments more aggressively in time.
>
> Signed-off-by: Yunlong Song <yunlong.song@huawei.com>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
> ---
> 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 d01ee7b94702..c27dab43c42f 100644
> --- a/fs/f2fs/segment.c
> +++ b/fs/f2fs/segment.c
> @@ -1541,7 +1541,7 @@ 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;
>
> - if (IS_NODESEG(type) || !has_not_enough_free_secs(sbi, 0, 0))
> + if (IS_NODESEG(type))
> return v_ops->get_victim(sbi,
> &(curseg)->next_segno, BG_GC, type, SSR);
>
--
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 1/3] f2fs: clean up codes in get_ssr_segment
Date: Thu, 23 Feb 2017 09:55:29 +0800 [thread overview]
Message-ID: <58AE4111.2070406@huawei.com> (raw)
In-Reply-To: <20170223005915.GG4003@jaegeuk.local>
Yes, exactly, I just mean it for short with word "clean up", thanks for correction.
On 2017/2/23 8:59, Jaegeuk Kim wrote:
> On 02/22, Jaegeuk Kim wrote:
>> Hi Yunlong,
>>
>> This is NOT clean-up. What's your point here?
> I guess you wanted to do like this.
>
> >From 8d344ac45890dd95c5734fd29a19a7c19364c327 Mon Sep 17 00:00:00 2001
> From: Yunlong Song <yunlong.song@huawei.com>
> Date: Wed, 22 Feb 2017 20:50:49 +0800
> Subject: [PATCH] f2fs: do SSR for data when there is enough free space
>
> In allocate_segment_by_default(), need_SSR() already detected it's time to do
> SSR. So, let's try to find victims for data segments more aggressively in time.
>
> Signed-off-by: Yunlong Song <yunlong.song@huawei.com>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
> ---
> 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 d01ee7b94702..c27dab43c42f 100644
> --- a/fs/f2fs/segment.c
> +++ b/fs/f2fs/segment.c
> @@ -1541,7 +1541,7 @@ 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;
>
> - if (IS_NODESEG(type) || !has_not_enough_free_secs(sbi, 0, 0))
> + if (IS_NODESEG(type))
> return v_ops->get_victim(sbi,
> &(curseg)->next_segno, BG_GC, type, SSR);
>
--
Thanks,
Yunlong Song
next prev parent reply other threads:[~2017-02-23 1:55 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
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 [this message]
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=58AE4111.2070406@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.