From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: wangzijie <wangzijie1@honor.com>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
feng.han@honor.com, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3 1/2] f2fs: avoid redundant clean nat entry move in lru list
Date: Mon, 28 Jul 2025 16:50:20 +0000 [thread overview]
Message-ID: <175372142024.776676.5036079944268949062.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250728050237.1563560-1-wangzijie1@honor.com>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 28 Jul 2025 13:02:35 +0800 you 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>
> ---
> v3:
> - followed by Chao's suggestion to update comments
> v2:
> - followed by Jaegeuk's suggestion to add a parameter in __lookup_nat_cache
>
> [...]
Here is the summary with links:
- [f2fs-dev,v3,1/2] f2fs: avoid redundant clean nat entry move in lru list
https://git.kernel.org/jaegeuk/f2fs/c/0349b7f95c80
- [f2fs-dev,v3,2/2] f2fs: directly add newly allocated pre-dirty nat entry to dirty set list
https://git.kernel.org/jaegeuk/f2fs/c/40aa9e1223fd
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
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: patchwork-bot+f2fs@kernel.org
To: wangzijie <wangzijie1@honor.com>
Cc: jaegeuk@kernel.org, chao@kernel.org,
linux-kernel@vger.kernel.org, feng.han@honor.com,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3 1/2] f2fs: avoid redundant clean nat entry move in lru list
Date: Mon, 28 Jul 2025 16:50:20 +0000 [thread overview]
Message-ID: <175372142024.776676.5036079944268949062.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250728050237.1563560-1-wangzijie1@honor.com>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 28 Jul 2025 13:02:35 +0800 you 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>
> ---
> v3:
> - followed by Chao's suggestion to update comments
> v2:
> - followed by Jaegeuk's suggestion to add a parameter in __lookup_nat_cache
>
> [...]
Here is the summary with links:
- [f2fs-dev,v3,1/2] f2fs: avoid redundant clean nat entry move in lru list
https://git.kernel.org/jaegeuk/f2fs/c/0349b7f95c80
- [f2fs-dev,v3,2/2] f2fs: directly add newly allocated pre-dirty nat entry to dirty set list
https://git.kernel.org/jaegeuk/f2fs/c/40aa9e1223fd
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-07-28 16:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 5:02 [f2fs-dev] [PATCH v3 1/2] f2fs: avoid redundant clean nat entry move in lru list wangzijie
2025-07-28 5:02 ` wangzijie
2025-07-28 5:02 ` [f2fs-dev] [PATCH v3 2/2] f2fs: directly add newly allocated pre-dirty nat entry to dirty set list wangzijie
2025-07-28 5:02 ` wangzijie
2025-07-28 7:47 ` Chao Yu via Linux-f2fs-devel
2025-07-28 7:47 ` Chao Yu
2025-07-28 7:39 ` [f2fs-dev] [PATCH v3 1/2] f2fs: avoid redundant clean nat entry move in lru list Chao Yu via Linux-f2fs-devel
2025-07-28 7:39 ` Chao Yu
2025-07-28 16:50 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
2025-07-28 16:50 ` 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=175372142024.776676.5036079944268949062.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=feng.han@honor.com \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@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 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.