From: Pablo de Lara <pablo.de.lara.guarch@intel.com>
To: declan.doherty@intel.com, jerin.jacob@caviumnetworks.com
Cc: dev@dpdk.org, Pablo de Lara <pablo.de.lara.guarch@intel.com>
Subject: [dpdk-dev] [PATCH 0/8] Remove temporary digest allocation
Date: Fri, 18 Aug 2017 08:20:55 +0100 [thread overview]
Message-ID: <20170818072103.1416-1-pablo.de.lara.guarch@intel.com> (raw)
When performing authentication verification,
some crypto PMDs require extra memory where the generated
digest can be placed.
Currently, these PMDs are getting the memory from the end
of the source mbuf, which might fail if there is not enough
tailroom.
To avoid this situation, some memory is allocated
in each queue pair of the device, to store temporarily
these digests.
Pablo de Lara (8):
crypto/aesni_gcm: do not append digest
crypto/armv8: do not append digest
crypto/openssl: do not append digest
crypto/kasumi: do not append digest
crypto/snow3g: do not append digest
crypto/zuc: do not append digest
crypto/aesni_mb: do not append digest
test/crypto: do not allocate extra memory for digest
drivers/crypto/aesni_gcm/aesni_gcm_pmd.c | 31 ++++---------------
drivers/crypto/aesni_gcm/aesni_gcm_pmd_private.h | 7 +++++
drivers/crypto/aesni_mb/rte_aesni_mb_pmd.c | 36 +++++++---------------
drivers/crypto/aesni_mb/rte_aesni_mb_pmd_ops.c | 5 +++
drivers/crypto/aesni_mb/rte_aesni_mb_pmd_private.h | 12 +++++++-
drivers/crypto/armv8/rte_armv8_pmd.c | 14 +++------
drivers/crypto/armv8/rte_armv8_pmd_private.h | 8 +++++
drivers/crypto/kasumi/rte_kasumi_pmd.c | 22 +++++--------
drivers/crypto/kasumi/rte_kasumi_pmd_private.h | 7 +++++
drivers/crypto/openssl/rte_openssl_pmd.c | 19 +++++-------
drivers/crypto/openssl/rte_openssl_pmd_private.h | 7 +++++
drivers/crypto/snow3g/rte_snow3g_pmd.c | 22 +++++--------
drivers/crypto/snow3g/rte_snow3g_pmd_private.h | 7 +++++
drivers/crypto/zuc/rte_zuc_pmd.c | 16 +++-------
drivers/crypto/zuc/rte_zuc_pmd_private.h | 7 +++++
test/test/test_cryptodev_blockcipher.c | 29 ++---------------
16 files changed, 112 insertions(+), 137 deletions(-)
--
2.9.4
next reply other threads:[~2017-08-18 15:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-18 7:20 Pablo de Lara [this message]
2017-08-18 7:20 ` [dpdk-dev] [PATCH 1/8] crypto/aesni_gcm: do not append digest Pablo de Lara
2017-09-04 10:07 ` Zhang, Roy Fan
2017-09-05 8:49 ` De Lara Guarch, Pablo
2017-08-18 7:20 ` [dpdk-dev] [PATCH 2/8] crypto/armv8: " Pablo de Lara
2017-09-11 5:22 ` Jerin Jacob
2017-08-18 7:20 ` [dpdk-dev] [PATCH 3/8] crypto/openssl: " Pablo de Lara
2017-08-18 7:20 ` [dpdk-dev] [PATCH 4/8] crypto/kasumi: " Pablo de Lara
2017-08-18 7:21 ` [dpdk-dev] [PATCH 5/8] crypto/snow3g: " Pablo de Lara
2017-08-18 7:21 ` [dpdk-dev] [PATCH 6/8] crypto/zuc: " Pablo de Lara
2017-08-18 7:21 ` [dpdk-dev] [PATCH 7/8] crypto/aesni_mb: " Pablo de Lara
2017-08-18 7:21 ` [dpdk-dev] [PATCH 8/8] test/crypto: do not allocate extra memory for digest Pablo de Lara
2017-09-05 2:19 ` [dpdk-dev] [PATCH v2 0/8] Remove temporary digest allocation Pablo de Lara
2017-09-05 2:20 ` [dpdk-dev] [PATCH v2 1/8] crypto/aesni_gcm: do not append digest Pablo de Lara
2017-09-05 2:20 ` [dpdk-dev] [PATCH v2 2/8] crypto/armv8: " Pablo de Lara
2017-09-06 9:02 ` De Lara Guarch, Pablo
2017-09-05 2:20 ` [dpdk-dev] [PATCH v2 3/8] crypto/openssl: " Pablo de Lara
2017-09-05 2:20 ` [dpdk-dev] [PATCH v2 4/8] crypto/kasumi: " Pablo de Lara
2017-09-05 2:20 ` [dpdk-dev] [PATCH v2 5/8] crypto/snow3g: " Pablo de Lara
2017-09-05 2:20 ` [dpdk-dev] [PATCH v2 6/8] crypto/zuc: " Pablo de Lara
2017-09-05 2:20 ` [dpdk-dev] [PATCH v2 7/8] crypto/aesni_mb: " Pablo de Lara
2017-09-05 2:20 ` [dpdk-dev] [PATCH v2 8/8] test/crypto: do not allocate extra memory for digest Pablo de Lara
2017-09-05 12:38 ` [dpdk-dev] [PATCH v2 0/8] Remove temporary digest allocation Zhang, Roy Fan
2017-09-11 9:39 ` De Lara Guarch, Pablo
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=20170818072103.1416-1-pablo.de.lara.guarch@intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=jerin.jacob@caviumnetworks.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).