From: Gao Xiang <xiang@kernel.org>
To: linux-erofs@lists.ozlabs.org, Li Guifu <bluce.liguifu@huawei.com>
Cc: Gao Xiang <xiang@kernel.org>
Subject: [PATCH 0/4] erofs-utils: prepare for per-(sub)file compression strategies
Date: Mon, 10 May 2021 15:22:59 +0800 [thread overview]
Message-ID: <20210510072303.4628-1-xiang@kernel.org> (raw)
Hi all,
This patchset mainly provides a new helper z_erofs_get_max_pclustersize()
to prepare for per-file compression strategies, valid pclustersize can be
returned according to detailed data type or access patterns.
In order to do that, compression header is now generated on the per-file
basis as well, which will be also needed for parallel compression in
the future.
Note that
https://lore.kernel.org/r/20210510064715.29123-1-xiang@kernel.org
should be applied after "erofs-utils: compress trailing data for big
pcluster properly" is used or some compress indexes won't be parsed
correctly.
Thanks,
Gao Xiang
Gao Xiang (4):
erofs-utils: compress trailing data for big pcluster properly
erofs-utils: reserve physical_clusterbits[]
erofs-utils: prepare for per-(sub)file compress strategies
erofs-utils: sync up z_erofs_get_extent_compressedlen()
include/erofs/internal.h | 1 -
lib/compress.c | 91 +++++++++++++++++++++++++++-------------
lib/compressor.c | 5 ++-
lib/zmap.c | 53 +++++++++++++----------
4 files changed, 96 insertions(+), 54 deletions(-)
--
2.20.1
next reply other threads:[~2021-05-10 7:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-10 7:22 Gao Xiang [this message]
2021-05-10 7:23 ` [PATCH 1/4] erofs-utils: compress trailing data for big pcluster properly Gao Xiang
2021-05-10 7:23 ` [PATCH 2/4] erofs-utils: reserve physical_clusterbits[] Gao Xiang
2021-05-10 7:23 ` [PATCH 3/4] erofs-utils: prepare for per-(sub)file compress strategies Gao Xiang
2021-05-10 7:23 ` [PATCH 4/4] erofs-utils: sync up z_erofs_get_extent_compressedlen() 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=20210510072303.4628-1-xiang@kernel.org \
--to=xiang@kernel.org \
--cc=bluce.liguifu@huawei.com \
--cc=linux-erofs@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).