From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Doherty, Declan" <declan.doherty@intel.com>,
"Griffin, John" <john.griffin@intel.com>,
"Jain, Deepak K" <deepak.k.jain@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH 2/5] doc: remove incorrect limitation on QAT PMD
Date: Fri, 14 Jul 2017 15:58:53 +0000 [thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B4358923665E@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <20170713053650.62998-3-pablo.de.lara.guarch@intel.com>
> -----Original Message-----
> From: De Lara Guarch, Pablo
> Sent: Thursday, July 13, 2017 6:37 AM
> To: Doherty, Declan <declan.doherty@intel.com>; Trahe, Fiona <fiona.trahe@intel.com>; Griffin, John
> <john.griffin@intel.com>; Jain, Deepak K <deepak.k.jain@intel.com>
> Cc: dev@dpdk.org; De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; stable@dpdk.org
> Subject: [PATCH 2/5] doc: remove incorrect limitation on QAT PMD
>
> QAT supports authentication only operations,
> for any authentication algorithm (such as SHA1-HMAC),
> as long as it is supported by QAT, so it means
> that it is not necessary to create a chained operation
> in order to use these algorithms.
>
> Fixes: 1703e94ac5ce ("qat: add driver for QuickAssist devices")
> CC: stable@dpdk.org
>
> Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
Acked-by: Fiona Trahe <fiona.trahe@intel.com>
next prev parent reply other threads:[~2017-07-14 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170713053650.62998-1-pablo.de.lara.guarch@intel.com>
2017-07-13 5:36 ` Pablo de Lara
2017-07-14 15:58 ` Trahe, Fiona [this message]
2017-07-13 5:36 ` [dpdk-stable] [PATCH 3/5] doc: remove incorrect limitation on AESNI MB PMD Pablo de Lara
2017-07-13 5:36 ` [dpdk-stable] [PATCH 4/5] doc: add missing algorithm in limitations for QAT Pablo de Lara
2017-07-14 16:13 ` Trahe, Fiona
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=348A99DA5F5B7549AA880327E580B4358923665E@IRSMSX101.ger.corp.intel.com \
--to=fiona.trahe@intel.com \
--cc=declan.doherty@intel.com \
--cc=deepak.k.jain@intel.com \
--cc=dev@dpdk.org \
--cc=john.griffin@intel.com \
--cc=pablo.de.lara.guarch@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).