From: Chao Yu <chao@kernel.org>
To: Daniel Lee <chullee@google.com>, Jaegeuk Kim <jaegeuk@kernel.org>
Cc: chao@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] f2fs: add lookup_mode mount option
Date: Tue, 5 Aug 2025 14:59:56 +0800 [thread overview]
Message-ID: <f2f8cbd8-af49-475b-8b9c-e00250263007@kernel.org> (raw)
In-Reply-To: <20250805065228.1473089-1-chullee@google.com>
On 8/5/25 14:52, Daniel Lee 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.
>
> This commit introduces the 'lookup_mode' mount option to provide this
> kernel-side control.
>
> The option accepts three values:
> - perf: (Default) Enforces a hash-only lookup. The linear fallback
> is always disabled.
> - compat: Enables the linear search fallback for compatibility with
> directory entries from older kernels.
> - auto: Determines the mode based on the on-disk flag, preserving the
> userspace-based behavior.
>
> Signed-off-by: Daniel Lee <chullee@google.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
next prev parent reply other threads:[~2025-08-05 7:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 6:52 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 ` Chao Yu [this message]
2025-08-15 16:40 ` [f2fs-dev] [PATCH v3 1/2] f2fs: add lookup_mode mount option 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=f2f8cbd8-af49-475b-8b9c-e00250263007@kernel.org \
--to=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
all inboxes | Powered by JetHome®