From: Gao Xiang <xiang@kernel.org>
To: linux-erofs@lists.ozlabs.org, Chao Yu <chao@kernel.org>
Cc: linux-kernel@vger.kernel.org, Gao Xiang <hsiangkao@linux.alibaba.com>
Subject: [PATCH 0/3] erofs: random decompression cleanups
Date: Sun, 29 May 2022 13:54:22 +0800 [thread overview]
Message-ID: <20220529055425.226363-1-xiang@kernel.org> (raw)
From: Gao Xiang <hsiangkao@linux.alibaba.com>
Hi folks,
Now I'm working on cleanuping decompression code and doing some
folio adaption for the next 5.20 cycle, see:
https://git.kernel.org/pub/scm/linux/kernel/git/xiang/linux.git/log/?h=erofs/folios
This cleanup work completely gets rid of PageError usage finally
and tries to prepare for introducing rolling hashing for EROFS
since EROFS supports compressing variable-sized data instead of
fixed-sized clusters.
Therefore, EROFS can support rolling hash easily and our mechanism
can make full use of filesystem interfaces (byte-addressed) naturally.
Before that, I'd like to submit some trivial cleanups in advance for
the 5.19 cycle. All patches are without any logical change, so I can
have a more recent codebase for the next rework cycle.
Thanks,
Gao Xiang
Gao Xiang (3):
erofs: get rid of `struct z_erofs_collection'
erofs: get rid of label `restart_now'
erofs: simplify z_erofs_pcluster_readmore()
fs/erofs/zdata.c | 165 +++++++++++++++++++----------------------------
fs/erofs/zdata.h | 50 +++++++-------
2 files changed, 88 insertions(+), 127 deletions(-)
--
2.30.2
next reply other threads:[~2022-05-29 5:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-29 5:54 Gao Xiang [this message]
2022-05-29 5:54 ` [PATCH 1/3] erofs: get rid of `struct z_erofs_collection' Gao Xiang
2022-05-29 5:54 ` [PATCH 2/3] erofs: get rid of label `restart_now' Gao Xiang
2022-05-29 5:54 ` [PATCH 3/3] erofs: simplify z_erofs_pcluster_readmore() Gao Xiang
2022-05-31 6:45 ` [PATCH 0/3] erofs: random decompression cleanups Chao Yu
2022-05-31 6:50 ` Gao Xiang
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=20220529055425.226363-1-xiang@kernel.org \
--to=xiang@kernel.org \
--cc=chao@kernel.org \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--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