From: Zhou Wang <wangzhou1@hisilicon.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: <linux-kernel@vger.kernel.org>, <linuxarm@huawei.com>,
<linux-crypto@vger.kernel.org>,
"David S . Miller" <davem@davemloft.net>
Subject: Re: [PATCH 3/4] crypto: hisilicon: Add HiSilicon ZIP accelerator support
Date: Fri, 18 Jan 2019 15:55:05 +0800 [thread overview]
Message-ID: <5C418659.30904@hisilicon.com> (raw)
In-Reply-To: <20190118045546.hs37a2isfnvxgm7j@gondor.apana.org.au>
On 2019/1/18 12:55, Herbert Xu wrote:
> On Wed, Jan 16, 2019 at 10:12:47PM +0800, Zhou Wang wrote:
>>
>> A stupid question: how do we test scomp alg?
>>
>> It seems we can not use general comp API, e.g. crypto_alloc_comp
>> to do this.
>>
>> Could you give me any clue about this?
>
> scomp algorithms are allocated through crypto_alloc_acomp.
A little strange, but let me try firstly.
However, another question is that seems other subsystems in kernel,
e.g. zswap still use crypto_alloc_comp. So we'd better register this
ZIP engine using both cryto_alloc_comp and scomp/acomp interface to
make it compatible with other subsystems?
Best,
Zhou
>
> Thanks,
>
next prev parent reply other threads:[~2019-01-18 7:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-22 7:51 [PATCH 0/4] crypto: hisilicon: Add HiSilicon QM and ZIP controller driver Zhou Wang
2018-12-22 7:51 ` [PATCH 1/4] Documentation: Add debugfs doc for hisi_zip Zhou Wang
2018-12-22 7:51 ` [PATCH 2/4] crypto: hisilicon: Add queue management driver for HiSilicon QM module Zhou Wang
2018-12-22 7:51 ` [PATCH 3/4] crypto: hisilicon: Add HiSilicon ZIP accelerator support Zhou Wang
2019-01-11 6:08 ` Herbert Xu
2019-01-11 6:34 ` Zhou Wang
2019-01-16 14:12 ` Zhou Wang
2019-01-18 4:55 ` Herbert Xu
2019-01-18 7:55 ` Zhou Wang [this message]
2019-01-18 10:09 ` Herbert Xu
2018-12-22 7:51 ` [PATCH 4/4] MAINTAINERS: add maintainer for HiSilicon QM and ZIP controller driver Zhou Wang
2019-01-10 6:30 ` [PATCH 0/4] crypto: hisilicon: Add " Zhou Wang
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=5C418659.30904@hisilicon.com \
--to=wangzhou1@hisilicon.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.