From: Gao Xiang <xiang@kernel.org> To: linux-erofs@lists.ozlabs.org Cc: Gao Xiang <xiang@kernel.org> Subject: [PATCH v2 2/3] erofs-utils: README: big pcluster feature update Date: Mon, 31 May 2021 22:31:16 +0800 [thread overview] Message-ID: <20210531143117.6327-2-xiang@kernel.org> (raw) In-Reply-To: <20210531143117.6327-1-xiang@kernel.org> Add some description for end users to know its usage. Link: https://lore.kernel.org/r/20210522055057.25004-2-xiang@kernel.org Signed-off-by: Gao Xiang <xiang@kernel.org> --- README | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/README b/README index bcf30e11aa52..af9cdf11c78a 100644 --- a/README +++ b/README @@ -74,6 +74,24 @@ In addition, you could specify a higher compression level to get a (slightly) better compression ratio than the default level, e.g. $ mkfs.erofs -zlz4hc,12 foo.erofs.img foo/ +How to generate EROFS big pcluster images (Linux 5.13+) +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +In order to get much better compression ratios (thus better sequential +read performance for common storage devices), big pluster feature has +been introduced since linux-5.13, which is not forward-compatible with +old kernels. + +In details, -C is used to specify the maximum size of each big pcluster +in bytes, e.g. + $ mkfs.erofs -zlz4hc -C65536 foo.erofs.img foo/ + +So in that case, pcluster size can be 64KiB at most. + +Note that large pcluster size can cause bad random performance, so +please evaluate carefully in advance. Or make your own per-(sub)file +compression strategies according to file access patterns if needed. + How to generate legacy EROFS images (Linux 4.19+) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -- 2.20.1
next prev parent reply other threads:[~2021-05-31 14:31 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-31 14:31 [PATCH v2 1/3] erofs-utils: README: trivial updates Gao Xiang 2021-05-31 14:31 ` Gao Xiang [this message] 2021-05-31 14:31 ` [PATCH v2 3/3] erofs-utils: support limit max decompressed extent size 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=20210531143117.6327-2-xiang@kernel.org \ --to=xiang@kernel.org \ --cc=linux-erofs@lists.ozlabs.org \ --subject='Re: [PATCH v2 2/3] erofs-utils: README: big pcluster feature update' \ /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
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).