From: Herbert Xu <herbert@gondor.apana.org.au>
To: Yang Shen <shenyang39@huawei.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
ardb@kernel.org, kees@kernel.org, linux-kernel@vger.kernel.org,
enlin.mu@unisoc.com, ebiggers@google.com, gpiccoli@igalia.com,
willy@infradead.org, yunlong.xing@unisoc.com,
yuxiaozhang@google.com,
Giovanni Cabiddu <giovanni.cabiddu@intel.com>,
qat-linux@intel.com,
Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
Zhou Wang <wangzhou1@hisilicon.com>
Subject: Re: [PATCH 1/4] crypto: hisilicon/zip - Remove driver
Date: Thu, 31 Aug 2023 13:42:30 +0800 [thread overview]
Message-ID: <ZPAoRvMYbsoNfnLk@gondor.apana.org.au> (raw)
In-Reply-To: <8a73f9cb-b1e8-3b54-4b6c-7cfb19244560@huawei.com>
On Thu, Aug 31, 2023 at 10:21:52AM +0800, Yang Shen wrote:
>
> It's a pity to see that there is no user in the kernel of zlib-deflate.
> However, there may still be hidden
> users in the current kernel who may be using the zlib-deflate algorithm.
> Such as zswap, it can use
> user-specified algorithm. So there are still some benefits to be gained from
> zlib hardware.
Perhaps you should try reconstructing the zlib header in your
driver so that it becomes capable of handling "deflate" data as
is rather than adding the non-standard "zlib-deflate" algorithm?
There is no way of getting the checksum without decompressing
the data first but perhaps your hardware could ignore checksum
errors?
> What's more, hisilicon zip driver also does other work besides supporting
> the zlib-deflate:
> 1.Support gzip algorithm.
We don't even have a generic "gzip" implementation so this should
never have gone into the kernel.
> 2.Support a user space cdev hisi-zip which can accelerate user space process
> via uacce subsystem.
Feel free to resubmit this as a new driver but it doesn't belong
in drivers/crypto.
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2023-08-31 5:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHk-=wgaY2+_KyqVpRS+MrO6Y7bXQp69odTu7JT3XSpdUsgS=g@mail.gmail.com>
[not found] ` <ZO8HcBirOZnX9iRs@gondor.apana.org.au>
2023-08-30 10:04 ` [PATCH 0/4] crypto: Remove zlib-deflate Herbert Xu
2023-08-30 10:08 ` [PATCH 1/4] crypto: hisilicon/zip - Remove driver Herbert Xu
2023-08-31 2:21 ` Yang Shen
2023-08-31 5:42 ` Herbert Xu [this message]
2023-08-31 9:39 ` Yang Shen
2023-08-31 11:57 ` Herbert Xu
2023-08-30 10:08 ` [PATCH 2/4] crypto: qat - Remove zlib-deflate Herbert Xu
2023-09-05 13:15 ` Giovanni Cabiddu
2023-09-05 16:23 ` David Sterba
2023-09-06 2:51 ` Gao Xiang
2023-08-30 10:08 ` [PATCH 3/4] crypto: deflate " Herbert Xu
2023-08-30 10:08 ` [PATCH 4/4] crypto: testmgr " Herbert Xu
2023-08-30 12:52 ` [PATCH 0/4] crypto: " Ard Biesheuvel
2023-08-30 15:29 ` Linus Torvalds
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=ZPAoRvMYbsoNfnLk@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=ardb@kernel.org \
--cc=ebiggers@google.com \
--cc=enlin.mu@unisoc.com \
--cc=giovanni.cabiddu@intel.com \
--cc=gpiccoli@igalia.com \
--cc=kees@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qat-linux@intel.com \
--cc=shenyang39@huawei.com \
--cc=torvalds@linux-foundation.org \
--cc=wangzhou1@hisilicon.com \
--cc=willy@infradead.org \
--cc=yunlong.xing@unisoc.com \
--cc=yuxiaozhang@google.com \
/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