From: Akhil Goyal <akhil.goyal@nxp.com>
To: Fan Zhang <roy.fan.zhang@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "arkadiuszx.kusztal@intel.com" <arkadiuszx.kusztal@intel.com>,
"pablo.de.lara.guarch@intel.com" <pablo.de.lara.guarch@intel.com>,
Fiona Trahe <fiona.trahe@intel.com>,
Paul Luse <paul.e.luse@intel.com>
Subject: Re: [dpdk-dev] [PATCH v3 0/2] crypto/aesni_mb: enable out of place processing
Date: Fri, 29 Mar 2019 14:37:13 +0000 [thread overview]
Message-ID: <05c210ea-04e9-2493-d615-320391d20e9c@nxp.com> (raw)
In-Reply-To: <20190325135121.4484-1-roy.fan.zhang@intel.com>
On 3/25/2019 7:21 PM, Fan Zhang wrote:
> Add out-of-place processing, i.e. different source and
> destination m_bufs, plus related capability update, tests
> and documentation.
>
> Signed-off-by: Fiona Trahe <fiona.trahe@intel.com>
> Signed-off-by: Paul Luse <paul.e.luse@intel.com>
> Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
>
> v3:
> - Updated unit test, enable src-dst swap test for all oop tests.
> - Merged patches.
> - Updated documentation.
> - Several code changes based on Pablo's comments.
>
> v2:
> - Removed limitation of not support cipher-auth.
> - Updated tests for more comprehensive test-cases.
> - Splitted the patch.
>
> Fan Zhang (2):
> crypto/aesni_mb: enable out of place processing
> test: add out of place test for AESNI-MB
>
> app/test/test_cryptodev_aes_test_vectors.h | 110 +++++++++++++++++++++++++---
> app/test/test_cryptodev_blockcipher.c | 83 ++++++++++++++++++---
> app/test/test_cryptodev_blockcipher.h | 3 +
> app/test/test_cryptodev_des_test_vectors.h | 24 ++++--
> doc/guides/cryptodevs/aesni_mb.rst | 1 -
> doc/guides/cryptodevs/features/aesni_mb.ini | 1 +
> doc/guides/rel_notes/release_19_05.rst | 4 +
> drivers/crypto/aesni_mb/rte_aesni_mb_pmd.c | 102 +++++++++++++++++++-------
> 8 files changed, 270 insertions(+), 58 deletions(-)
>
Applied to dpdk-next-crypto
Thanks.
next prev parent reply other threads:[~2019-03-29 14:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 11:36 [dpdk-dev] [PATCH v2 0/3] " Fan Zhang
2019-02-28 11:36 ` [dpdk-dev] [PATCH v2 1/3] " Fan Zhang
2019-03-19 17:18 ` Trahe, Fiona
2019-03-19 17:18 ` Trahe, Fiona
2019-03-20 17:52 ` De Lara Guarch, Pablo
2019-03-20 17:52 ` De Lara Guarch, Pablo
2019-02-28 11:36 ` [dpdk-dev] [PATCH v2 2/3] test: add out of place test for AESNI-MB Fan Zhang
2019-03-19 17:28 ` Trahe, Fiona
2019-03-19 17:28 ` Trahe, Fiona
2019-02-28 11:36 ` [dpdk-dev] [PATCH v2 3/3] doc: update documentation Fan Zhang
2019-03-19 17:29 ` Trahe, Fiona
2019-03-19 17:29 ` Trahe, Fiona
2019-03-20 17:55 ` De Lara Guarch, Pablo
2019-03-20 17:55 ` De Lara Guarch, Pablo
2019-03-25 13:51 ` [dpdk-dev] [PATCH v3 0/2] crypto/aesni_mb: enable out of place processing Fan Zhang
2019-03-25 13:51 ` Fan Zhang
2019-03-25 13:51 ` [dpdk-dev] [PATCH v3 1/2] " Fan Zhang
2019-03-25 13:51 ` Fan Zhang
2019-03-25 13:51 ` [dpdk-dev] [PATCH v3 2/2] test: add out of place test for AESNI-MB Fan Zhang
2019-03-25 13:51 ` Fan Zhang
2019-03-29 14:37 ` Akhil Goyal [this message]
2019-03-29 14:37 ` [dpdk-dev] [PATCH v3 0/2] crypto/aesni_mb: enable out of place processing Akhil Goyal
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=05c210ea-04e9-2493-d615-320391d20e9c@nxp.com \
--to=akhil.goyal@nxp.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=paul.e.luse@intel.com \
--cc=roy.fan.zhang@intel.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).