From: patchwork-bot+f2fs@kernel.org
To: Chao Yu <chao@kernel.org>
Cc: jaegeuk@kernel.org, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: use f2fs_{down, up}_(read, write}_trace() for nat_tree_lock
Date: Fri, 21 Aug 2026 15:50:07 +0000 [thread overview]
Message-ID: <178732740714.1339488.2738118422362472739.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260817111916.1648354-1-chao@kernel.org>
Hello:
This patch was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 17 Aug 2026 11:19:16 +0000 you wrote:
> Under heavy workloads or during background GC/fallocate operations,
> nat_tree_lock can experience high lock contention between background
> readers (e.g. f2fs_get_node_info() in gc_data_segment) and writers
> (e.g. flush_nat_entries, set_node_addr, shrinker).
>
> [375067.327986][T13777] schedule+0x4c/0x114
> [375067.327997][T13777] f2fs_get_node_info+0x438/0x5c4
> [375067.328002][T13777] f2fs_get_inode_page+0x1e0/0x3f0
> [375067.328013][T13777] f2fs_iget+0x88/0x1180
> [375067.328024][T13777] f2fs_lookup+0x168/0x3a8
> [375067.328035][T13777] path_openat+0xa28/0x1b04
> [375067.328046][T13777] do_filp_open+0xac/0x130
> [375067.328056][T13777] do_sys_openat2+0x140/0x21c
> [375067.328066][T13777] __arm64_sys_openat+0x70/0x9c
>
> [...]
Here is the summary with links:
- [f2fs-dev] f2fs: use f2fs_{down, up}_(read, write}_trace() for nat_tree_lock
https://git.kernel.org/jaegeuk/f2fs/c/f9c899ec50ab
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-08-21 15:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-17 11:19 [PATCH] f2fs: use f2fs_{down,up}_(read,write}_trace() for nat_tree_lock Chao Yu
2026-08-21 15:50 ` patchwork-bot+f2fs [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=178732740714.1339488.2738118422362472739.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=jaegeuk@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