From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Jaegeuk Kim <jaegeuk@kernel.org>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: refactor f2fs_evict_inode having three major parts
Date: Tue, 11 Aug 2026 09:48:26 +0800 [thread overview]
Message-ID: <43d7f2ef-ddb4-46af-ab6d-eda8d15a4983@kernel.org> (raw)
In-Reply-To: <20260807220235.384637-1-jaegeuk@kernel.org>
On 8/8/26 06:02, Jaegeuk Kim via Linux-f2fs-devel wrote:
> 1. f2fs_pre_evict_inode()
> : drop all in-memory structures
>
> 2. f2fs_delete_inode()
> : truncate inode blocks, if it was unlinked.
>
> 3. f2fs_post_evict_inode()
> : update inode records for future access
That's a good cleanup! more clear now.
>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Cc: chao@kernel.org
Subject: Re: [f2fs-dev] [PATCH 1/2] f2fs: refactor f2fs_evict_inode having three major parts
Date: Tue, 11 Aug 2026 09:48:26 +0800 [thread overview]
Message-ID: <43d7f2ef-ddb4-46af-ab6d-eda8d15a4983@kernel.org> (raw)
In-Reply-To: <20260807220235.384637-1-jaegeuk@kernel.org>
On 8/8/26 06:02, Jaegeuk Kim via Linux-f2fs-devel wrote:
> 1. f2fs_pre_evict_inode()
> : drop all in-memory structures
>
> 2. f2fs_delete_inode()
> : truncate inode blocks, if it was unlinked.
>
> 3. f2fs_post_evict_inode()
> : update inode records for future access
That's a good cleanup! more clear now.
>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2026-08-11 1:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 22:02 [PATCH 1/2] f2fs: refactor f2fs_evict_inode having three major parts Jaegeuk Kim
2026-08-07 22:02 ` [f2fs-dev] " Jaegeuk Kim via Linux-f2fs-devel
2026-08-07 22:02 ` [PATCH 2/2] f2fs: call __add_ino_entry out of the eviction path Jaegeuk Kim
2026-08-07 22:02 ` [f2fs-dev] " Jaegeuk Kim via Linux-f2fs-devel
2026-08-11 1:49 ` Chao Yu
2026-08-11 1:49 ` Chao Yu via Linux-f2fs-devel
2026-08-11 1:48 ` Chao Yu via Linux-f2fs-devel [this message]
2026-08-11 1:48 ` [f2fs-dev] [PATCH 1/2] f2fs: refactor f2fs_evict_inode having three major parts Chao Yu
2026-08-11 4:30 ` patchwork-bot+f2fs
2026-08-11 4:30 ` patchwork-bot+f2fs--- via Linux-f2fs-devel
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=43d7f2ef-ddb4-46af-ab6d-eda8d15a4983@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--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 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.