From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: wangzijie <wangzijie1@honor.com>, jaegeuk@kernel.org
Cc: linux-kernel@vger.kernel.org, feng.han@honor.com,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2 1/2] f2fs: avoid redundant clean nat entry move in lru list
Date: Thu, 24 Jul 2025 14:00:33 +0800 [thread overview]
Message-ID: <b17f5401-0462-42c7-8fef-0875814d1064@kernel.org> (raw)
In-Reply-To: <20250722143628.430776-1-wangzijie1@honor.com>
On 7/22/25 22:36, wangzijie wrote:
> __lookup_nat_cache follows LRU manner to move clean nat entry, when nat
> entries are going to be dirty, no need to move them to tail of lru list.
> Introduce a parameter 'for_dirty' to avoid it.
>
> Signed-off-by: wangzijie <wangzijie1@honor.com>
> ---
> v2:
> - followed by Jaegeuk's suggestion to add a parameter in __lookup_nat_cache
> ---
> fs/f2fs/node.c | 24 ++++++++++++------------
> 1 file changed, 12 insertions(+), 12 deletions(-)
>
> diff --git a/fs/f2fs/node.c b/fs/f2fs/node.c
> index 76aba1961..a23db6238 100644
> --- a/fs/f2fs/node.c
> +++ b/fs/f2fs/node.c
> @@ -204,14 +204,14 @@ static struct nat_entry *__init_nat_entry(struct f2fs_nm_info *nm_i,
> return ne;
> }
>
> -static struct nat_entry *__lookup_nat_cache(struct f2fs_nm_info *nm_i, nid_t n)
> +static struct nat_entry *__lookup_nat_cache(struct f2fs_nm_info *nm_i, nid_t n, bool for_dirty)
> {
> struct nat_entry *ne;
>
> ne = radix_tree_lookup(&nm_i->nat_root, n);
>
> - /* for recent accessed nat entry, move it to tail of lru list */
> - if (ne && !get_nat_flag(ne, IS_DIRTY)) {
> + /* for recent accessed(not used to set dirty) nat entry, move it to tail of lru list */
What do you think of this?
/*
* for recent accessed nat entry which will not be dirtied soon
* later, move it to tail of lru list.
*/
Thanks,
> + if (ne && !get_nat_flag(ne, IS_DIRTY) && !for_dirty) {
> spin_lock(&nm_i->nat_list_lock);
> if (!list_empty(&ne->list))
> list_move_tail(&ne->list, &nm_i->nat_entries);
> @@ -383,7 +383,7 @@ int f2fs_need_dentry_mark(struct f2fs_sb_info *sbi, nid_t nid)
> bool need = false;
>
> f2fs_down_read(&nm_i->nat_tree_lock);
> - e = __lookup_nat_cache(nm_i, nid);
> + e = __lookup_nat_cache(nm_i, nid, false);
> if (e) {
> if (!get_nat_flag(e, IS_CHECKPOINTED) &&
> !get_nat_flag(e, HAS_FSYNCED_INODE))
> @@ -400,7 +400,7 @@ bool f2fs_is_checkpointed_node(struct f2fs_sb_info *sbi, nid_t nid)
> bool is_cp = true;
>
> f2fs_down_read(&nm_i->nat_tree_lock);
> - e = __lookup_nat_cache(nm_i, nid);
> + e = __lookup_nat_cache(nm_i, nid, false);
> if (e && !get_nat_flag(e, IS_CHECKPOINTED))
> is_cp = false;
> f2fs_up_read(&nm_i->nat_tree_lock);
> @@ -414,7 +414,7 @@ bool f2fs_need_inode_block_update(struct f2fs_sb_info *sbi, nid_t ino)
> bool need_update = true;
>
> f2fs_down_read(&nm_i->nat_tree_lock);
> - e = __lookup_nat_cache(nm_i, ino);
> + e = __lookup_nat_cache(nm_i, ino, false);
> if (e && get_nat_flag(e, HAS_LAST_FSYNC) &&
> (get_nat_flag(e, IS_CHECKPOINTED) ||
> get_nat_flag(e, HAS_FSYNCED_INODE)))
> @@ -439,7 +439,7 @@ static void cache_nat_entry(struct f2fs_sb_info *sbi, nid_t nid,
> return;
>
> f2fs_down_write(&nm_i->nat_tree_lock);
> - e = __lookup_nat_cache(nm_i, nid);
> + e = __lookup_nat_cache(nm_i, nid, false);
> if (!e)
> e = __init_nat_entry(nm_i, new, ne, false);
> else
> @@ -460,7 +460,7 @@ static void set_node_addr(struct f2fs_sb_info *sbi, struct node_info *ni,
> struct nat_entry *new = __alloc_nat_entry(sbi, ni->nid, true);
>
> f2fs_down_write(&nm_i->nat_tree_lock);
> - e = __lookup_nat_cache(nm_i, ni->nid);
> + e = __lookup_nat_cache(nm_i, ni->nid, true);
> if (!e) {
> e = __init_nat_entry(nm_i, new, NULL, true);
> copy_node_info(&e->ni, ni);
> @@ -502,7 +502,7 @@ static void set_node_addr(struct f2fs_sb_info *sbi, struct node_info *ni,
>
> /* update fsync_mark if its inode nat entry is still alive */
> if (ni->nid != ni->ino)
> - e = __lookup_nat_cache(nm_i, ni->ino);
> + e = __lookup_nat_cache(nm_i, ni->ino, false);
> if (e) {
> if (fsync_done && ni->nid == ni->ino)
> set_nat_flag(e, HAS_FSYNCED_INODE, true);
> @@ -562,7 +562,7 @@ int f2fs_get_node_info(struct f2fs_sb_info *sbi, nid_t nid,
> retry:
> /* Check nat cache */
> f2fs_down_read(&nm_i->nat_tree_lock);
> - e = __lookup_nat_cache(nm_i, nid);
> + e = __lookup_nat_cache(nm_i, nid, false);
> if (e) {
> ni->ino = nat_get_ino(e);
> ni->blk_addr = nat_get_blkaddr(e);
> @@ -2371,7 +2371,7 @@ static bool add_free_nid(struct f2fs_sb_info *sbi,
> * - __remove_nid_from_list(PREALLOC_NID)
> * - __insert_nid_to_list(FREE_NID)
> */
> - ne = __lookup_nat_cache(nm_i, nid);
> + ne = __lookup_nat_cache(nm_i, nid, false);
> if (ne && (!get_nat_flag(ne, IS_CHECKPOINTED) ||
> nat_get_blkaddr(ne) != NULL_ADDR))
> goto err_out;
> @@ -2936,7 +2936,7 @@ static void remove_nats_in_journal(struct f2fs_sb_info *sbi)
>
> raw_ne = nat_in_journal(journal, i);
>
> - ne = __lookup_nat_cache(nm_i, nid);
> + ne = __lookup_nat_cache(nm_i, nid, true);
> if (!ne) {
> ne = __alloc_nat_entry(sbi, nid, true);
> __init_nat_entry(nm_i, ne, &raw_ne, true);
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2025-07-24 6:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 14:36 [f2fs-dev] [PATCH v2 1/2] f2fs: avoid redundant clean nat entry move in lru list wangzijie
2025-07-22 14:36 ` [f2fs-dev] [PATCH v2 2/2] f2fs: directly add newly allocated pre-dirty nat entry to dirty set list wangzijie
2025-07-24 8:26 ` Chao Yu via Linux-f2fs-devel
2025-07-25 2:17 ` wangzijie
2025-07-25 2:36 ` Chao Yu via Linux-f2fs-devel
2025-07-24 6:00 ` Chao Yu via Linux-f2fs-devel [this message]
2025-07-24 6:57 ` [f2fs-dev] [PATCH v2 1/2] f2fs: avoid redundant clean nat entry move in lru list wangzijie
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=b17f5401-0462-42c7-8fef-0875814d1064@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=feng.han@honor.com \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangzijie1@honor.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).