From: patchwork-bot+f2fs--- via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Cen Zhang <zzzccc427@gmail.com>
Cc: baijiaju1990@gmail.com, jaegeuk@kernel.org,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: annotate lockless NAT counter reads
Date: Mon, 11 May 2026 01:41:09 +0000 [thread overview]
Message-ID: <177846366929.1975880.13898644322342059326.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260505125510.1369132-1-zzzccc427@gmail.com>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Tue, 5 May 2026 20:55:10 +0800 you wrote:
> nat_cnt[] is updated while callers hold nat_tree_lock, but F2FS samples
> the counters locklessly in f2fs_available_free_memory(),
> excess_dirty_nats(), and excess_cached_nats(). Those helpers only steer
> cache reclaim and background sync heuristics; they do not control NAT
> entry lifetime or checkpoint correctness.
>
> Document the intent with data_race(READ_ONCE()) and a short comment
> instead of adding locking to the balance path.
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: annotate lockless NAT counter reads
https://git.kernel.org/jaegeuk/f2fs/c/e2b659d3f6ce
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
prev parent reply other threads:[~2026-05-11 1:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 12:55 [f2fs-dev] [PATCH] f2fs: annotate lockless NAT counter reads Cen Zhang
2026-05-09 13:17 ` Chao Yu via Linux-f2fs-devel
2026-05-11 1:41 ` patchwork-bot+f2fs--- via Linux-f2fs-devel [this message]
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=177846366929.1975880.13898644322342059326.git-patchwork-notify@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=baijiaju1990@gmail.com \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patchwork-bot+f2fs@kernel.org \
--cc=zzzccc427@gmail.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