From: Gao Xiang <hsiangkao@redhat.com>
To: linux-erofs@lists.ozlabs.org
Subject: Re: [RFC PATCH v0 0/3] erofs-utils: support multiple block compression
Date: Wed, 30 Dec 2020 18:12:39 +0800 [thread overview]
Message-ID: <20201230101239.GA3282742@xiangao.remote.csb> (raw)
In-Reply-To: <20201230084728.813-1-hsiangkao@aol.com>
On Wed, Dec 30, 2020 at 04:47:25PM +0800, Gao Xiang via Linux-erofs wrote:
> From: Gao Xiang <hsiangkao@aol.com>
>
> Hi folks,
>
> This is the first RFC patch of multiple block compression (including
> erofsfuse) after I carefully think over the on-disk design to support
> multiblock in-place decompression.
>
> Compression ratio results (POC, lz4hc, lz4-1.9.3, not final result):
> 1000000000 enwik9
> 621211648 enwik9_4k.squashfs.img
> 557858816 enwik9_4k.erofs.img
> 556191744 enwik9_8k.squashfs.img
> 502661120 enwik9_16k.squashfs.img
> 500723712 enwik9_8k.erofs.img
> 458784768 enwik9_32k.squashfs.img
> 453971968 enwik9_16k.erofs.img
> 422318080 enwik9_64k.squashfs.img
> 416686080 enwik9_32k.erofs.img
> 398204928 enwik9_128k.squashfs.img
> 395276288 enwik9_64k.erofs.img
I can also think out several compress strategies to control read amplification
but maintain a given C/R due to EROFS can compress variable-sized input data
to arbitary compressed block count for each pcluster, FYI.
Thanks,
Gao Xiang
prev parent reply other threads:[~2020-12-30 10:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201230084728.813-1-hsiangkao.ref@aol.com>
2020-12-30 8:47 ` [RFC PATCH v0 0/3] erofs-utils: support multiple block compression Gao Xiang via Linux-erofs
2020-12-30 8:47 ` [RFC PATCH v0 1/3] erofs-utils: add -C# for the maximum size of pclusters Gao Xiang via Linux-erofs
2020-12-30 8:47 ` [RFC PATCH v0 2/3] erofs-utils: mkfs: support multiple block compression Gao Xiang via Linux-erofs
2020-12-30 8:47 ` [RFC PATCH v0 3/3] erofs-utils: fuse: " Gao Xiang via Linux-erofs
2020-12-30 10:12 ` Gao Xiang [this message]
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=20201230101239.GA3282742@xiangao.remote.csb \
--to=hsiangkao@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.