From: Nithurshen <nithurshen.dev@gmail.com>
To: nithurshen.dev@gmail.com
Cc: hsiangkao@linux.alibaba.com, linux-erofs@lists.ozlabs.org,
xiang@kernel.org
Subject: [PATCH v3 0/2] fsck.erofs: add multi-threaded decompression
Date: Tue, 9 Jun 2026 14:47:41 +0530 [thread overview]
Message-ID: <20260609091743.71420-1-nithurshen.dev@gmail.com> (raw)
In-Reply-To: <20260523003757.13078-1-nithurshen.dev@gmail.com>
Hi Xiang,
Thank you for the detailed review of v2. I have addressed all the structural
and style comments in this v3 series:
1. Extracted erofs_cond_t wrappers into a separate include/erofs/cond.h.
2. Replaced sysconf() with erofs_get_available_processors().
3. Refactored the parallel arrays in the decompression task into a clean
struct z_erofs_decompress_item array for better memory layout.
4. Fixed all indentation (enforced tabs) and single-statement conditionals/gotos.
This series introduces multi-threaded decompression to fsck.erofs to
decouple I/O from decompression, significantly improving extraction
throughput on multicore systems.
Thanks,
Nithurshen
Nithurshen (2):
fsck.erofs: introduce multi-threaded decompression with static
batching
fsck.erofs: implement algorithm-aware pcluster batching
fsck/main.c | 150 ++++++++++++---------------
include/erofs/cond.h | 31 ++++++
include/erofs/internal.h | 20 +++-
include/erofs/lock.h | 3 +
lib/data.c | 216 +++++++++++++++++++++++++++++----------
5 files changed, 277 insertions(+), 143 deletions(-)
create mode 100644 include/erofs/cond.h
--
2.52.0
next prev parent reply other threads:[~2026-06-09 9:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-23 0:37 [PATCH 0/2] fsck.erofs: introduce multi-threaded decompression Nithurshen
2026-05-23 0:37 ` [PATCH 1/2] fsck.erofs: introduce multi-threaded decompression with static batching Nithurshen
2026-06-07 1:50 ` Gao Xiang
2026-05-23 0:37 ` [PATCH 2/2] fsck.erofs: implement dynamic pcluster batching based on algorithm complexity Nithurshen
2026-06-07 1:52 ` Gao Xiang
2026-06-08 5:07 ` [PATCH v2 0/2] fsck.erofs: add multi-threaded decompression Nithurshen
2026-06-08 5:07 ` [PATCH v2 1/2] fsck.erofs: introduce multi-threaded decompression with static batching Nithurshen
2026-06-08 6:25 ` Gao Xiang
2026-06-08 5:07 ` [PATCH v2 2/2] fsck.erofs: implement algorithm-aware pcluster batching Nithurshen
2026-06-09 9:17 ` Nithurshen [this message]
2026-06-09 9:17 ` [PATCH v3 1/2] fsck.erofs: introduce multi-threaded decompression with static batching Nithurshen
2026-06-09 9:17 ` [PATCH v3 2/2] fsck.erofs: implement algorithm-aware pcluster batching Nithurshen
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=20260609091743.71420-1-nithurshen.dev@gmail.com \
--to=nithurshen.dev@gmail.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=xiang@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