mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chi Zhiling <chizhiling@163.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Namjae Jeon <linkinjeon@kernel.org>,
	Sungjong Seo <sj1557.seo@samsung.com>,
	Yuezhang Mo <yuezhang.mo@sony.com>,
	Chi Zhiling <chizhiling@kylinos.cn>
Subject: [PATCH v2 0/6] exfat: improve performance of NO_FAT_CHAIN to FAT_CHAIN conversion
Date: Tue,  3 Mar 2026 11:14:03 +0800	[thread overview]
Message-ID: <20260303031409.129136-1-chizhiling@163.com> (raw)

From: Chi Zhiling <chizhiling@kylinos.cn>

This series improves the performance when converting files from NO_FAT_CHAIN
to FAT_CHAIN format (which happens when a file cannot allocate contiguous
clusters). It also adds proper error handling for FAT table write operations.

- Patch 1: Add block readahead for FAT blocks during conversion
- Patch 2-3: Refactor existing readahead code to use the new helper
- Patch 4: Remove redundant sec parameter from exfat_mirror_bh
- Patch 5: Cache buffer heads to reduce mark_buffer_dirty overhead
- Patch 6: Fix error handling to propagate FAT write errors to callers

Performance improvements for converting a 30GB file:

| Cluster Size | Before | After  | Speedup |
|--------------|--------|--------|---------|
| 512 bytes    | 47.667s| 1.866s | 25.5x   |
| 4KB          | 6.436s | 0.236s | 27.3x   |
| 32KB         | 0.758s | 0.034s | 22.3x   |
| 256KB        | 0.117s | 0.006s | 19.5x   |

v1: https://lore.kernel.org/all/20260204071435.602246-1-chizhiling@163.com/

Chi Zhiling (6):
  exfat: add block readahead in exfat_chain_cont_cluster
  exfat: use readahead helper in exfat_allocate_bitmap
  exfat: use readahead helper in exfat_get_dentry
  exfat: drop redundant sec parameter from exfat_mirror_bh
  exfat: optimize exfat_chain_cont_cluster with cached buffer heads
  exfat: fix error handling for FAT table operations

 fs/exfat/balloc.c   | 18 +++------
 fs/exfat/dir.c      | 52 +++++++------------------
 fs/exfat/exfat_fs.h | 13 +++++--
 fs/exfat/fatent.c   | 95 ++++++++++++++++++++++++++++++++++++---------
 fs/exfat/inode.c    |  5 ++-
 fs/exfat/misc.c     |  8 +++-
 fs/exfat/namei.c    |  3 +-
 7 files changed, 118 insertions(+), 76 deletions(-)

-- 
2.43.0


             reply	other threads:[~2026-03-03  3:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-03  3:14 Chi Zhiling [this message]
2026-03-03  3:14 ` [PATCH v2 1/6] exfat: add block readahead in exfat_chain_cont_cluster Chi Zhiling
2026-03-03  3:14 ` [PATCH v2 2/6] exfat: use readahead helper in exfat_allocate_bitmap Chi Zhiling
2026-03-03  3:14 ` [PATCH v2 3/6] exfat: use readahead helper in exfat_get_dentry Chi Zhiling
2026-03-03  3:14 ` [PATCH v2 4/6] exfat: drop redundant sec parameter from exfat_mirror_bh Chi Zhiling
2026-03-03  3:14 ` [PATCH v2 5/6] exfat: optimize exfat_chain_cont_cluster with cached buffer heads Chi Zhiling
2026-03-03  3:14 ` [PATCH v2 6/6] exfat: fix error handling for FAT table operations Chi Zhiling
2026-03-05 12:15 ` [PATCH v2 0/6] exfat: improve performance of NO_FAT_CHAIN to FAT_CHAIN conversion Namjae Jeon

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=20260303031409.129136-1-chizhiling@163.com \
    --to=chizhiling@163.com \
    --cc=chizhiling@kylinos.cn \
    --cc=linkinjeon@kernel.org \
    --cc=linux-fsdevel@vger.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®