From: Zhou Wang <wangzhou1@hisilicon.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "David S . Miller" <davem@davemloft.net>,
<linux-crypto@vger.kernel.org>, <linuxarm@huawei.com>,
<linux-kernel@vger.kernel.org>,
Kenneth Lee <liguozhu@hisilicon.com>,
Shiju Jose <shiju.jose@huawei.com>,
Hao Fang <fanghao11@huawei.com>
Subject: Re: [PATCH v2 2/4] crypto: hisilicon: Add queue management driver for HiSilicon QM module
Date: Wed, 20 Feb 2019 14:50:01 +0800 [thread overview]
Message-ID: <5C6CF899.1020708@hisilicon.com> (raw)
In-Reply-To: <20190220041011.oob4e7jk3fwoqjlg@gondor.apana.org.au>
On 2019/2/20 12:10, Herbert Xu wrote:
> On Sat, Feb 02, 2019 at 10:25:43AM +0800, Zhou Wang wrote:
>>
>> In fact, I planned to register to acomp later.
>>
>> It also makes sense to use scomp if hardware engine is faster than CPU.
>> So how about registering to scomp firstly, then we register this engine to
>> acomp later?
>
> Sorry, but the fact that you're doing a busy-wait for completion
> means that scomp is not an appropriate choice.
OK. I will use acomp in next version.
Thanks,
Zhou
>
> Cheers,
>
next prev parent reply other threads:[~2019-02-20 6:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 13:08 [PATCH v2 0/4] crypto: hisilicon: Add HiSilicon QM and ZIP controller driver Zhou Wang
2019-01-23 13:08 ` [PATCH v2 1/4] Documentation: Add debugfs doc for hisi_zip Zhou Wang
2019-01-23 13:08 ` [PATCH v2 2/4] crypto: hisilicon: Add queue management driver for HiSilicon QM module Zhou Wang
2019-02-01 5:22 ` Herbert Xu
2019-02-01 7:15 ` Zhou Wang
2019-02-01 15:39 ` Herbert Xu
2019-02-02 2:25 ` Zhou Wang
2019-02-20 4:10 ` Herbert Xu
2019-02-20 6:50 ` Zhou Wang [this message]
2019-01-23 13:08 ` [PATCH v2 3/4] crypto: hisilicon: Add HiSilicon ZIP accelerator support Zhou Wang
2019-01-23 13:08 ` [PATCH v2 4/4] MAINTAINERS: add maintainer for HiSilicon QM and ZIP controller driver Zhou Wang
2019-01-29 1:19 ` [PATCH v2 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=5C6CF899.1020708@hisilicon.com \
--to=wangzhou1@hisilicon.com \
--cc=davem@davemloft.net \
--cc=fanghao11@huawei.com \
--cc=herbert@gondor.apana.org.au \
--cc=liguozhu@hisilicon.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=shiju.jose@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).