From: Jaegeuk Kim <jaegeuk@kernel.org>
To: Chao Yu <chao@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: allocate HOT_DATA for IPU writes
Date: Thu, 28 Aug 2025 15:23:09 +0000 [thread overview]
Message-ID: <aLB0XeQh_tm2tXIA@google.com> (raw)
In-Reply-To: <bfbd5db4-c103-4a08-8568-1d27c8eba676@kernel.org>
On 08/28, Chao Yu wrote:
> 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?
This deals with IPU in the LFS mode.
>
> Thanks,
>
> >
> > Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.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);
next prev parent reply other threads:[~2025-08-28 15:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 21:52 Jaegeuk Kim
2025-08-28 3:31 ` [f2fs-dev] " Chao Yu
2025-08-28 15:23 ` Jaegeuk Kim [this message]
2025-08-28 23:17 ` Chao Yu
2025-08-29 20:47 ` Jaegeuk Kim
2025-08-30 1:11 ` Chao Yu
2025-08-30 23:54 ` Jaegeuk Kim
2025-09-01 2:15 ` Chao Yu
2025-09-02 20:20 ` patchwork-bot+f2fs
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=aLB0XeQh_tm2tXIA@google.com \
--to=jaegeuk@kernel.org \
--cc=chao@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®