From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Eric Biggers <ebiggers@kernel.org>, Bo Liu <liubo03@inspur.com>
Cc: xiang@kernel.org, chao@kernel.org, linux-erofs@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] erofs: support deflate decompress by using Intel QAT
Date: Sat, 17 May 2025 11:28:14 +0800 [thread overview]
Message-ID: <2e076b62-0b6a-4af3-a8c2-babade16fa6d@linux.alibaba.com> (raw)
In-Reply-To: <20250516163857.GA1241@sol>
Hi Eric,
On 2025/5/17 00:38, Eric Biggers wrote:
> On Fri, May 16, 2025 at 04:26:34AM -0400, Bo Liu wrote:
>> +config EROFS_FS_ZIP_CRYPTO
>> + bool "EROFS hardware decompression support (crypto interface)"
>> + depends on EROFS_FS_ZIP
>> + help
>> + Saying Y here includes support for reading EROFS file systems
>> + containing crypto compressed data. It gives better decompression
>> + speed than the software-implemented compression, and it costs
>> + lower CPU overhead.
>> +
>> + Crypto support is an experimental feature for now and so most
>> + file systems will be readable without selecting this option.
>> +
>> + If unsure, say N.
>
> I recommend not including the word "crypto" in any user facing part of this.
>
> Compression algorithms are not cryptographic algorithms. The fact that the
> interface to access hardware compression accelerators is currently the "Crypto
> API" is an implementation quirk. It could be a different interface in the
> future.
>
> Call it something clear like "hardware decompression".
Totally agreed on this since it's just an implementation detail,
and I will try to make some extra time to polish this commit myself
to fix some minor issues later.
Thanks,
Gao Xiang
>
> - Eric
next prev parent reply other threads:[~2025-05-17 3:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 8:26 [PATCH v3] erofs: support deflate decompress by using Intel QAT Bo Liu
2025-05-16 16:38 ` Eric Biggers
2025-05-17 3:28 ` Gao Xiang [this message]
2025-05-19 2:37 ` [External Mail][PATCH " Huang Jianan
2025-05-21 10:03 ` [PATCH UNTESTED v4] erofs: support DEFLATE decompression " 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=2e076b62-0b6a-4af3-a8c2-babade16fa6d@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=chao@kernel.org \
--cc=ebiggers@kernel.org \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liubo03@inspur.com \
--cc=xiang@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