[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bfbd5db4-c103-4a08-8568-1d27c8eba676@kernel.org>
Date: Thu, 28 Aug 2025 11:31:37 +0800
From: Chao Yu <chao@...nel.org>
To: Jaegeuk Kim <jaegeuk@...nel.org>, linux-kernel@...r.kernel.org,
linux-f2fs-devel@...ts.sourceforge.net
Cc: chao@...nel.org
Subject: Re: [f2fs-dev] [PATCH] f2fs: allocate HOT_DATA for IPU writes
On 8/28/25 05:52, Jaegeuk Kim via Linux-f2fs-devel wrote:
> Let's split IPU writes in hot data area to improve the GC efficiency.
I didn't get it, IPU may be not friendly for migrating data along w/ write in
hot area?
Thanks,
>
> Signed-off-by: Jaegeuk Kim <jaegeuk@...nel.org>
> ---
> fs/f2fs/segment.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
> index e0f6589c6a1c..bb79dad55ac9 100644
> --- a/fs/f2fs/segment.c
> +++ b/fs/f2fs/segment.c
> @@ -3688,7 +3688,8 @@ static int __get_segment_type_6(struct f2fs_io_info *fio)
>
> if (file_is_hot(inode) ||
> is_inode_flag_set(inode, FI_HOT_DATA) ||
> - f2fs_is_cow_file(inode))
> + f2fs_is_cow_file(inode) ||
> + is_inode_flag_set(inode, FI_NEED_IPU))
> return CURSEG_HOT_DATA;
> return f2fs_rw_hint_to_seg_type(F2FS_I_SB(inode),
> inode->i_write_hint);
Powered by blists - more mailing lists