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 v4 3/5] erofs-utils: manpage: add missing -C option for big pcluster
Date: Fri, 30 Apr 2021 12:03:43 +0800 [thread overview]
Message-ID: <20210430040345.17120-3-xiang@kernel.org> (raw)
In-Reply-To: <20210430040345.17120-1-xiang@kernel.org>
Update the manpage as well.
Signed-off-by: Gao Xiang <xiang@kernel.org>
---
man/mkfs.erofs.1 | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/man/mkfs.erofs.1 b/man/mkfs.erofs.1
index 2520b6a08974..4f2e43565799 100644
--- a/man/mkfs.erofs.1
+++ b/man/mkfs.erofs.1
@@ -24,6 +24,10 @@ from \fISOURCE\fR directory.
Set an algorithm for file compression, which can be set with an optional
compression level separated by a comma.
.TP
+.BI "\-C " max-pcluster-size
+Specify the maximum size of compress physical cluster in bytes. It may enable
+big pcluster feature if needed (Linux v5.13+).
+.TP
.BI "\-d " #
Specify the level of debugging messages. The default is 2, which shows basic
warning messages.
--
2.20.1
next prev parent reply other threads:[~2021-04-30 4:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 4:03 [PATCH v4 1/5] erofs-utils: sync up with in-kernel erofs_fs.h Gao Xiang
2021-04-30 4:03 ` [PATCH v4 2/5] erofs-utils: warn out experimental big pcluster Gao Xiang
2021-04-30 16:16 ` Li GuiFu via Linux-erofs
2021-04-30 4:03 ` Gao Xiang [this message]
2021-04-30 16:16 ` [PATCH v4 3/5] erofs-utils: manpage: add missing -C option for " Li GuiFu via Linux-erofs
2021-04-30 4:03 ` [PATCH v4 4/5] erofs-utils: zero out garbage trailing data for non-0padding cases Gao Xiang
2021-04-30 16:17 ` Li GuiFu via Linux-erofs
2021-04-30 4:03 ` [PATCH v4 5/5] erofs-utils: manpage: add manual for erofsfuse Gao Xiang
2021-04-30 16:17 ` Li GuiFu via Linux-erofs
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=20210430040345.17120-3-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).