From: Ayuj Verma <ayverma@marvell.com>
To: <akhil.goyal@nxp.com>
Cc: <arkadiuszx.kusztal@intel.com>, <shallyv@marvell.com>,
<ssahu@marvell.com>, <kkotamarthy@marvell.com>,
<anoobj@marvell.com>, <dev@dpdk.org>,
Ayuj Verma <ayverma@marvell.com>
Subject: [dpdk-dev] [PATCH v1 0/2] declare crypto asym xform immutable
Date: Wed, 24 Jul 2019 14:21:55 +0530 [thread overview]
Message-ID: <1563958317-480-1-git-send-email-ayverma@marvell.com> (raw)
Mark asym xform as immutable till lifetime
of session. It will save session setup time for
PMDs, which doesn't require any manipulation of
xform data, by directly using these buffers.
* Updated xform type in session init/configure
API as constant.
* Updated doc with proper transform description.
* Updated openssl PMD with above changes.
Ayuj Verma (2):
lib/crypto: declare crypto asym xform immutable
crypto/openssl: mark asym xform constant
doc/guides/prog_guide/cryptodev_lib.rst | 10 ++++++++++
drivers/crypto/openssl/rte_openssl_pmd_ops.c | 8 ++++----
lib/librte_cryptodev/rte_cryptodev.c | 2 +-
lib/librte_cryptodev/rte_cryptodev.h | 2 +-
lib/librte_cryptodev/rte_cryptodev_pmd.h | 2 +-
5 files changed, 17 insertions(+), 7 deletions(-)
--
1.8.3.1
next reply other threads:[~2019-07-24 8:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 8:51 Ayuj Verma [this message]
2019-07-24 8:51 ` [dpdk-dev] [PATCH v1 1/2] lib/crypto: " Ayuj Verma
2019-07-24 8:51 ` [dpdk-dev] [PATCH v1 2/2] crypto/openssl: mark asym xform constant Ayuj Verma
2019-07-24 8:52 ` [dpdk-dev] [PATCH v1 0/2] declare crypto asym xform immutable Ayuj Verma
2019-07-25 4:15 ` Anoob Joseph
2019-07-25 5:21 ` Shally Verma
2019-07-25 5:26 ` Anoob Joseph
2019-07-25 6:37 ` Anoob Joseph
2019-07-25 7:58 ` Shally Verma
2019-07-25 14:27 ` Kusztal, ArkadiuszX
2019-07-29 11:38 ` Ayuj Verma
2019-09-05 9:22 ` Kusztal, ArkadiuszX
2019-09-05 14:22 ` Shally Verma
2019-09-06 6:08 ` Anoob Joseph
2019-09-06 11:25 ` Trahe, Fiona
2019-09-13 14:02 ` Sunila Sahu
2019-09-13 14:59 ` Kusztal, ArkadiuszX
2019-07-25 11:27 ` Akhil Goyal
2019-07-25 11:35 ` Shally Verma
2019-07-25 11:42 ` Akhil Goyal
2019-07-25 11:46 ` Shally Verma
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=1563958317-480-1-git-send-email-ayverma@marvell.com \
--to=ayverma@marvell.com \
--cc=akhil.goyal@nxp.com \
--cc=anoobj@marvell.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=kkotamarthy@marvell.com \
--cc=shallyv@marvell.com \
--cc=ssahu@marvell.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).