From: Chao Yu <chao@kernel.org>
To: Gao Xiang <hsiangkao@linux.alibaba.com>, linux-erofs@lists.ozlabs.org
Cc: chao@kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] erofs: update the Kconfig description
Date: Mon, 23 Mar 2026 17:59:42 +0800 [thread overview]
Message-ID: <927c52ee-24b5-4b8f-98ee-3a18f13fa8b5@kernel.org> (raw)
In-Reply-To: <20260323094857.2187994-1-hsiangkao@linux.alibaba.com>
On 3/23/26 17:48, Gao Xiang wrote:
> Refine the description to better highlight its features and use cases.
>
> In addition, add instructions for building it as a module and clarify
> the compression option.
>
> Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>
> ---
> fs/erofs/Kconfig | 45 ++++++++++++++++++++++++++++++---------------
> 1 file changed, 30 insertions(+), 15 deletions(-)
>
> diff --git a/fs/erofs/Kconfig b/fs/erofs/Kconfig
> index a9f645f57bb2..9489ed8ad95b 100644
> --- a/fs/erofs/Kconfig
> +++ b/fs/erofs/Kconfig
> @@ -16,22 +16,36 @@ config EROFS_FS
> select ZLIB_INFLATE if EROFS_FS_ZIP_DEFLATE
> select ZSTD_DECOMPRESS if EROFS_FS_ZIP_ZSTD
> help
> - EROFS (Enhanced Read-Only File System) is a lightweight read-only
> - file system with modern designs (e.g. no buffer heads, inline
> - xattrs/data, chunk-based deduplication, multiple devices, etc.) for
> - scenarios which need high-performance read-only solutions, e.g.
> - smartphones with Android OS, LiveCDs and high-density hosts with
> - numerous containers;
> -
> - It also provides transparent compression and deduplication support to
> - improve storage density and maintain relatively high compression
> - ratios, and it implements in-place decompression to temporarily reuse
> - page cache for compressed data using proper strategies, which is
> - quite useful for ensuring guaranteed end-to-end runtime decompression
> + EROFS (Enhanced Read-Only File System) is a modern, lightweight,
> + secure read-only filesystem for various use cases, such as immutable
> + system images, container images, application sandboxes, and datasets.
> +
> + EROFS uses a flexible, hierarchical on-disk design so that features
> + can be enabled on demand: the core on-disk format is block-aligned in
> + order to perform optimally on all kinds of devices, including block
> + and memory-backed devices; the format is easy to parse and has zero
> + metadata redundancy, unlike generic filesystems, making it ideal for
> + for filesytem auditing and remote access; inline data, random-access
duplicated 'for'? otherwise, looks good to me.
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
> + friendly directory data, inline/shared extended attributes and
> + chunk-based deduplication ensure space efficiency while maintaining
> + high performance.
> +
> + Optionally, it supports multiple devices to reference external data,
> + enabling data sharing for container images.
> +
> + It also has advanced encoded on-disk layouts, particularly for data
> + compression and fine-grained deduplication. It utilizes fixed-size
> + output compression to improve storage density while keeping relatively
> + high compression ratios. Furthermore, it implements in-place
> + decompression to reuse file pages to keep compressed data temporarily
> + with proper strategies, which ensures guaranteed end-to-end runtime
> performance under extreme memory pressure without extra cost.
>
> - See the documentation at <file:Documentation/filesystems/erofs.rst>
> - and the web pages at <https://erofs.docs.kernel.org> for more details.
> + For more details, see the web pages at <https://erofs.docs.kernel.org>
> + and the documentation at <file:Documentation/filesystems/erofs.rst>.
> +
> + To compile EROFS filesystem support as a module, choose M here. The
> + module will be called erofs.
>
> If unsure, say N.
>
> @@ -105,7 +119,8 @@ config EROFS_FS_ZIP
> depends on EROFS_FS
> default y
> help
> - Enable transparent compression support for EROFS file systems.
> + Enable EROFS compression layouts so that filesystems containing
> + compressed files can be parsed by the kernel.
>
> If you don't want to enable compression feature, say N.
>
next prev parent reply other threads:[~2026-03-23 9:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 9:48 [PATCH] erofs: update the Kconfig description Gao Xiang
2026-03-23 9:59 ` Chao Yu [this message]
2026-03-23 15:33 ` 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=927c52ee-24b5-4b8f-98ee-3a18f13fa8b5@kernel.org \
--to=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