From: patchwork-bot+f2fs@kernel.org
To: Daniel Lee <chullee@google.com>
Cc: jaegeuk@kernel.org, chao@kernel.org,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v3 1/2] f2fs: add lookup_mode mount option
Date: Fri, 15 Aug 2025 16:40:11 +0000 [thread overview]
Message-ID: <175527601124.1161945.12842294818231800884.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250805065228.1473089-1-chullee@google.com>
Hello:
This series was applied to jaegeuk/f2fs.git (dev)
by Jaegeuk Kim <jaegeuk@kernel.org>:
On Mon, 4 Aug 2025 23:52:26 -0700 you wrote:
> For casefolded directories, f2fs may fall back to a linear search if
> a hash-based lookup fails. This can cause severe performance
> regressions.
>
> While this behavior can be controlled by userspace tools (e.g. mkfs,
> fsck) by setting an on-disk flag, a kernel-level solution is needed
> to guarantee the lookup behavior regardless of the on-disk state.
>
> [...]
Here is the summary with links:
- [f2fs-dev,v3,1/2] f2fs: add lookup_mode mount option
https://git.kernel.org/jaegeuk/f2fs/c/632f0b6c3e32
- [f2fs-dev,v3,2/2] f2fs: add sysfs entry for effective lookup mode
https://git.kernel.org/jaegeuk/f2fs/c/1bd119da0b93
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:[~2025-08-15 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 6:52 [PATCH v3 1/2] f2fs: add lookup_mode mount option Daniel Lee
2025-08-05 6:52 ` [PATCH v3 2/2] f2fs: add sysfs entry for effective lookup mode Daniel Lee
2025-08-05 7:00 ` Chao Yu
2025-08-05 6:59 ` [PATCH v3 1/2] f2fs: add lookup_mode mount option Chao Yu
2025-08-15 16:40 ` 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=175527601124.1161945.12842294818231800884.git-patchwork-notify@kernel.org \
--to=patchwork-bot+f2fs@kernel.org \
--cc=chao@kernel.org \
--cc=chullee@google.com \
--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;
as well as URLs for NNTP newsgroup(s).