From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Chao Yu <chao@kernel.org>, linux-erofs@lists.ozlabs.org
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] erofs: update the Kconfig description
Date: Mon, 23 Mar 2026 23:33:33 +0800 [thread overview]
Message-ID: <0a4bd05f-9a3d-4cf9-b36e-f49f729f0430@linux.alibaba.com> (raw)
In-Reply-To: <927c52ee-24b5-4b8f-98ee-3a18f13fa8b5@kernel.org>
Hi Chao,
On 2026/3/23 17:59, Chao Yu wrote:
> 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.
Fixed and thanks for the review!
>
> Reviewed-by: Chao Yu <chao@kernel.org>
>
> Thanks,
Thanks,
Gao Xiang
prev parent reply other threads:[~2026-03-23 15:33 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
2026-03-23 15:33 ` 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=0a4bd05f-9a3d-4cf9-b36e-f49f729f0430@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=chao@kernel.org \
--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