All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chao Yu <yuchao0@huawei.com>
To: Weichao Guo <guoweichao@oppo.com>, <jaegeuk@kernel.org>,
	<chao@kernel.org>
Cc: fh@oppo.com, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [RFC PATCH] f2fs: do not use CURSEG_ALL_DATA_ATGC in foreground or urgent GC
Date: Wed, 17 Mar 2021 10:40:07 +0800	[thread overview]
Message-ID: <88f444a3-0fc4-8b8b-4ab3-2c744fc06e01@huawei.com> (raw)
In-Reply-To: <1615900522-20747-1-git-send-email-guoweichao@oppo.com>

On 2021/3/16 21:15, Weichao Guo via Linux-f2fs-devel wrote:
> CURSEG_ALL_DATA_ATGC is introduced by age threshold based GC for better
> hot/cold data seperation and avoiding free segment cost. However, LFS
> write mode is preferred in the scenario of foreground or urgent GC, which
> should be finished ASAP. So, let's only use CURSEG_ALL_DATA_ATGC when not
> urgent in background GC.

Weichao,

select_gc_type()

	case GC_URGENT_HIGH:
		gc_mode = GC_GREEDY;

We have selected 'greedy' algorithm rather than 'atgc' algorithm for high
urgent gc, did you mean we should use 'greedy' for low urgent gc as well?

Thanks,

> 
> Signed-off-by: Weichao Guo <guoweichao@oppo.com>
> Signed-off-by: Huang Jianan <huangjianan@oppo.com>
> ---
>   fs/f2fs/gc.c      | 3 ++-
>   fs/f2fs/segment.c | 4 +++-
>   2 files changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/f2fs/gc.c b/fs/f2fs/gc.c
> index 86ba8ed..ee42f6e 100644
> --- a/fs/f2fs/gc.c
> +++ b/fs/f2fs/gc.c
> @@ -1120,7 +1120,8 @@ static int move_data_block(struct inode *inode, block_t bidx,
>   	block_t newaddr;
>   	int err = 0;
>   	bool lfs_mode = f2fs_lfs_mode(fio.sbi);
> -	int type = fio.sbi->am.atgc_enabled ?
> +	int type = fio.sbi->am.atgc_enabled && gc_type == BG_GC &&
> +				fio.sbi->gc_mode < GC_URGENT_HIGH ?
>   				CURSEG_ALL_DATA_ATGC : CURSEG_COLD_DATA;
>   
>   	/* do not read out */
> diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
> index 32b915e..cbfb0d1 100644
> --- a/fs/f2fs/segment.c
> +++ b/fs/f2fs/segment.c
> @@ -3264,7 +3264,9 @@ static int __get_segment_type_6(struct f2fs_io_info *fio)
>   		struct inode *inode = fio->page->mapping->host;
>   
>   		if (is_cold_data(fio->page)) {
> -			if (fio->sbi->am.atgc_enabled)
> +			if (fio->sbi->am.atgc_enabled &&
> +				fio->io_type == FS_DATA_IO &&
> +				fio->sbi->gc_mode < GC_URGENT_HIGH)
>   				return CURSEG_ALL_DATA_ATGC;
>   			else
>   				return CURSEG_COLD_DATA;
> 


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2021-03-17  2:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-16 13:15 [f2fs-dev] [RFC PATCH] f2fs: do not use CURSEG_ALL_DATA_ATGC in foreground or urgent GC Weichao Guo via Linux-f2fs-devel
2021-03-17  2:40 ` Chao Yu [this message]
2021-03-17  3:44   ` Weichao Guo via Linux-f2fs-devel
2021-03-17  6:41     ` Chao Yu
2021-03-17  7:01       ` Weichao Guo via Linux-f2fs-devel
2021-03-17  7:24         ` Chao Yu

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=88f444a3-0fc4-8b8b-4ab3-2c744fc06e01@huawei.com \
    --to=yuchao0@huawei.com \
    --cc=chao@kernel.org \
    --cc=fh@oppo.com \
    --cc=guoweichao@oppo.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    /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.