From: Chao Yu <chao@kernel.org>
To: Daniel Lee <chullee@google.com>
Cc: chao@kernel.org, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
Gabriel Krisman Bertazi <krisman@suse.de>
Subject: Re: [PATCH] f2fs: support to disable linear lookup fallback
Date: Tue, 1 Apr 2025 10:26:13 +0800 [thread overview]
Message-ID: <bef1588f-9c76-44a7-9b33-72ec307ae79d@kernel.org> (raw)
In-Reply-To: <CALBjLoDnzALdShsEzii6pK+fxgbeNVh8weKVtb=PyFJ3XgS1NA@mail.gmail.com>
On 4/1/25 00:31, Daniel Lee wrote:
> On Sun, Mar 30, 2025 at 7:54 PM Chao Yu <chao@kernel.org> wrote:
>>
>> After commit 91b587ba79e1 ("f2fs: Introduce linear search for
>> dentries"), f2fs forced to use linear lookup whenever a hash-based
>> lookup fails on casefolded directory, it may affect performance
>> for scenarios: a) create a new file w/ filename it doesn't exist
>> in directory, b) lookup a file which may be removed.
>>
>> This patch supports to disable linear lookup fallback, so, once there
>> is a solution for commit 5c26d2f1d3f5 ("unicode: Don't special case
>> ignorable code points") to fix red heart unicode issue, then we can
>> set an encodeing flag to disable the fallback for performance recovery.
>>
>> The way is kept in line w/ ext4, refer to commit 9e28059d5664 ("ext4:
>> introduce linear search for dentries").
>>
>> Cc: Daniel Lee <chullee@google.com>
>> Cc: Gabriel Krisman Bertazi <krisman@suse.de>
>> Signed-off-by: Chao Yu <chao@kernel.org>
>> ---
>> fs/f2fs/dir.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/fs/f2fs/dir.c b/fs/f2fs/dir.c
>> index 5a63ff0df03b..e12445afb95a 100644
>> --- a/fs/f2fs/dir.c
>> +++ b/fs/f2fs/dir.c
>> @@ -366,7 +366,8 @@ struct f2fs_dir_entry *__f2fs_find_entry(struct inode *dir,
>>
>> out:
>> #if IS_ENABLED(CONFIG_UNICODE)
>> - if (IS_CASEFOLDED(dir) && !de && use_hash) {
>> + if (IS_CASEFOLDED(dir) && !de && use_hash &&
>> + !sb_no_casefold_compat_fallback(dir->i_sb)) {
>
>
> Would it be beneficial to evaluate
> !sb_no_casefold_compat_fallback(dir->i_sb) first for short-circuiting?
Yeah, I guess it will when we disable the fallback by default, will update v2,
thank you!
Thanks,
>
>
>>
>> use_hash = false;
>> goto start_find_entry;
>> }
>> --
>> 2.49.0
>>
prev parent reply other threads:[~2025-04-01 2:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-31 2:54 Chao Yu
2025-03-31 16:31 ` Daniel Lee
2025-04-01 2:26 ` Chao Yu [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=bef1588f-9c76-44a7-9b33-72ec307ae79d@kernel.org \
--to=chao@kernel.org \
--cc=chullee@google.com \
--cc=jaegeuk@kernel.org \
--cc=krisman@suse.de \
--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®