From: Yang Wen <anmuxixixi@gmail.com>
To: linkinjeon@kernel.org, sj1557.seo@samsung.com, chizhiling@163.com
Cc: yuezhang.mo@sony.com, exfat@lists.linux.dev,
linux-kernel@vger.kernel.org, Yang Wen <anmuxixixi@gmail.com>
Subject: [PATCH v5 0/3] exfat: speed up file creation in large directories
Date: Sat, 19 Sep 2026 23:22:37 +0800 [thread overview]
Message-ID: <20260919152240.1507914-1-anmuxixixi@gmail.com> (raw)
Negative name lookups and empty-entry allocation can repeatedly scan a
directory from the beginning. Bulk creation in a large directory therefore
approaches O(N^2).
This series separates the optimization into three independently reviewable
steps. Patch 1 adds the Bloom filter used to reject definite name misses.
Patch 2 retains and correctly invalidates the next-empty-entry hint.
Patch 3 adds the LRU and shrinker used to reclaim filters under
memory pressure.
Test environment:
QEMU TCG multi-thread, 4 vCPUs, 6 GiB RAM
4 GiB exFAT image, 32 KiB clusters
The measured results were:
Before After
real 589.48 s 15.94 s
user 4.72 s 4.20 s
sys 584.63 s 11.71 s
Changes in v5:
- Rebase the series onto the exFAT maintainer's dev branch.
- Treat every non-negative exfat_find_empty_entry() return value as a
successful allocation in the volume-label path.
- Record the minimum entry-set size for which a saved empty-entry hint is
valid. A shorter entry set now rescans from the beginning and can reuse a
smaller hole that an earlier, longer entry set could not use.
Changes in v4:
- Publish the next-empty-entry hint only after the directory entry set is
successfully committed, so post-allocation failures cannot skip an unused
slot.
- Invalidate the destination name filter when rename or move fails because
the new entry may already exist on disk.
Changes in v3:
- Split the change into Bloom filter, empty-entry hint, and
shrinker patches.
- Accept filenames containing exactly 255 UTF-16 code units while building
the Bloom filter.
- Invalidate the empty-entry hint in every path that can free directory
entries, preventing stale hints from skipping earlier holes.
Changes in v2:
- Move exfat_name_filter_free() to exfat_evict_inode() because
->free_inode() may run from an RCU callback in softirq context.
Yang Wen (3):
exfat: add a Bloom filter for negative name lookups
exfat: retain the next empty directory entry hint
exfat: reclaim name filters under memory pressure
fs/exfat/dir.c | 293 +++++++++++++++++++++++++++++++++++++++++++-
fs/exfat/exfat_fs.h | 28 ++++-
fs/exfat/inode.c | 1 +
fs/exfat/namei.c | 86 +++++++++++--
fs/exfat/super.c | 9 ++
5 files changed, 408 insertions(+), 9 deletions(-)
--
2.34.1
next reply other threads:[~2026-09-19 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-19 15:22 Yang Wen [this message]
2026-09-19 15:22 ` [PATCH v5 1/3] exfat: add a Bloom filter for negative name lookups Yang Wen
2026-09-19 15:22 ` [PATCH v5 2/3] exfat: retain the next empty directory entry hint Yang Wen
2026-09-19 15:22 ` [PATCH v5 3/3] exfat: reclaim name filters under memory pressure Yang Wen
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=20260919152240.1507914-1-anmuxixixi@gmail.com \
--to=anmuxixixi@gmail.com \
--cc=chizhiling@163.com \
--cc=exfat@lists.linux.dev \
--cc=linkinjeon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sj1557.seo@samsung.com \
--cc=yuezhang.mo@sony.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
all inboxes | Powered by JetHome®