From: Herbert Xu <herbert@gondor.apana.org.au>
To: Zaibo Xu <xuzaibo@huawei.com>
Cc: davem@davemloft.net, linux-crypto@vger.kernel.org,
linuxarm@huawei.com, jonathan.cameron@huawei.com,
wangzhou1@hisilicon.com, tanghui20@huawei.com,
yekai13@huawei.com, liulongfang@huawei.com, qianweili@huawei.com,
zhangwei375@huawei.com, fanghao11@huawei.com,
forest.zhouchang@huawei.com
Subject: Re: [PATCH v3 0/5] crypto: hisilicon - Improve SEC performance
Date: Thu, 12 Mar 2020 23:39:13 +1100 [thread overview]
Message-ID: <20200312123913.GD28885@gondor.apana.org.au> (raw)
In-Reply-To: <1583373985-718-1-git-send-email-xuzaibo@huawei.com>
On Thu, Mar 05, 2020 at 10:06:20AM +0800, Zaibo Xu wrote:
> From: Longfang Liu <liulongfang@huawei.com>
>
> Improve SEC throughput by allocating a workqueue for each device
> instead of one workqueue for all SEC devices. What's more,
> when IOMMU translation is turned on, the plat buffer (pbuffer)
> will be reserved for small packets (<512Bytes) to
> which small packets are copied. This can avoid DMA mapping on
> user small packets and improve performance.
>
> This series is based on:
> git://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git
>
> Changes v2 -> v3:
> - Updated some comments and commit messages from Jonathan Cameron.
> - Removed CPU intensive workqueue flag WQ_CPU_INTENSIVE
> - Some small misc fixes.
>
> Changes v1 -> v2:
> - Split pbuf patch into two patches.
> - Move 'use_pbuf' from 'qp_ctx' to TFM request.
> - Misc fixes on coding style.
>
> Longfang Liu (3):
> crypto: hisilicon/sec2 - Add iommu status check
> crypto: hisilicon/sec2 - Update IV and MAC operation
> crypto: hisilicon/sec2 - Add pbuffer mode for SEC driver
>
> Shukun Tan (1):
> crypto: hisilicon - Use one workqueue per qm instead of per qp
>
> Ye Kai (1):
> crypto: hisilicon/sec2 - Add workqueue for SEC driver.
>
> drivers/crypto/hisilicon/qm.c | 39 ++---
> drivers/crypto/hisilicon/qm.h | 5 +-
> drivers/crypto/hisilicon/sec2/sec.h | 7 +
> drivers/crypto/hisilicon/sec2/sec_crypto.c | 242 ++++++++++++++++++++++++-----
> drivers/crypto/hisilicon/sec2/sec_main.c | 51 +++++-
> 5 files changed, 281 insertions(+), 63 deletions(-)
All applied. Thanks.
--
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
prev parent reply other threads:[~2020-03-12 12:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 2:06 [PATCH v3 0/5] crypto: hisilicon - Improve SEC performance Zaibo Xu
2020-03-05 2:06 ` [PATCH v3 1/5] crypto: hisilicon - Use one workqueue per qm instead of per qp Zaibo Xu
2020-03-05 2:06 ` [PATCH v3 2/5] crypto: hisilicon/sec2 - Add workqueue for SEC driver Zaibo Xu
2020-03-05 2:06 ` [PATCH v3 3/5] crypto: hisilicon/sec2 - Add iommu status check Zaibo Xu
2020-03-05 2:06 ` [PATCH v3 4/5] crypto: hisilicon/sec2 - Update IV and MAC operation Zaibo Xu
2020-03-05 2:06 ` [PATCH v3 5/5] crypto: hisilicon/sec2 - Add pbuffer mode for SEC driver Zaibo Xu
2020-03-12 12:39 ` Herbert Xu [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=20200312123913.GD28885@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=davem@davemloft.net \
--cc=fanghao11@huawei.com \
--cc=forest.zhouchang@huawei.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=liulongfang@huawei.com \
--cc=qianweili@huawei.com \
--cc=tanghui20@huawei.com \
--cc=wangzhou1@hisilicon.com \
--cc=xuzaibo@huawei.com \
--cc=yekai13@huawei.com \
--cc=zhangwei375@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).