From: Luca Boccassi <bluca@debian.org>
To: Adam Dybkowski <adamx.dybkowski@intel.com>,
stable@dpdk.org, fiona.trahe@intel.com
Subject: Re: [dpdk-stable] [PATCH 19.11 1/4] crypto/qat: handle mixed hash-cipher requests on GEN3
Date: Thu, 06 Aug 2020 11:00:00 +0100 [thread overview]
Message-ID: <19558b2cd5219d0de67f0589d5f3cf6b66c88ae0.camel@debian.org> (raw)
In-Reply-To: <20200729142252.177-1-adamx.dybkowski@intel.com>
On Wed, 2020-07-29 at 16:22 +0200, Adam Dybkowski wrote:
> [ upstream commit bcd7e3e8e6e18ce94c8aa02b949fc0274bd1faeb ]
>
> This patch implements handling mixed encrypted digest hash-cipher
> requests (e.g. SNOW3G + ZUC or ZUC + AES CTR) possible when running
> on GEN3 QAT. Such algorithm combinations are not supported on
> GEN1/GEN2 hardware.
>
> Signed-off-by: Adam Dybkowski <adamx.dybkowski@intel.com>
> Acked-by: Fiona Trahe <fiona.trahe@intel.com>
> ---
> doc/guides/cryptodevs/qat.rst | 24 ++++++++
> drivers/common/qat/qat_adf/icp_qat_fw.h | 3 +
> drivers/common/qat/qat_adf/icp_qat_fw_la.h | 2 +
> drivers/crypto/qat/qat_sym_session.c | 72 ++++++++++++++++++++++
> 4 files changed, 101 insertions(+)
Thanks, series applied - with the understanding that it's a PMD-
internal change that is backward/forward compatible.
--
Kind regards,
Luca Boccassi
prev parent reply other threads:[~2020-08-06 10:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-29 14:22 Adam Dybkowski
2020-07-29 14:22 ` [dpdk-stable] [PATCH 19.11 2/4] test/crypto: add mixed encypted-digest Adam Dybkowski
2020-07-29 14:22 ` [dpdk-stable] [PATCH 19.11 3/4] common/qat: get firmware version Adam Dybkowski
2020-07-29 14:22 ` [dpdk-stable] [PATCH 19.11 4/4] crypto/qat: handle mixed hash-cipher on GEN2 Adam Dybkowski
2020-08-06 10:00 ` Luca Boccassi [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=19558b2cd5219d0de67f0589d5f3cf6b66c88ae0.camel@debian.org \
--to=bluca@debian.org \
--cc=adamx.dybkowski@intel.com \
--cc=fiona.trahe@intel.com \
--cc=stable@dpdk.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;
as well as URLs for NNTP newsgroup(s).