From: Ayuj Verma <ayverma@marvell.com>
To: <akhil.goyal@nxp.com>
Cc: <arkadiuszx.kusztal@intel.com>, <fiona.trahe@intel.com>,
<shallyv@marvell.com>, <ssahu@marvell.com>,
<kkotamarthy@marvell.com>, <dev@dpdk.org>,
Ayuj Verma <ayverma@marvell.com>
Subject: [dpdk-dev] [RFC] mark asym session-buffer non-reuseable
Date: Wed, 17 Jul 2019 18:04:11 +0530 [thread overview]
Message-ID: <1563366852-23118-1-git-send-email-ayverma@marvell.com> (raw)
This RFC proposes changes in asymmetric session usability of
transform structure. In current implementation asym xform is
seen as temporary entity that can be re-used by application
once sessions are initialized with it.
This enforces PMD to copy all key buffers during session setup
time. Since life-time of sessions are small, so we can hold
these buffers with session, reducing memcpy time by marking these as
read-only so that PMDs which doesn’t require any manipulation of
xform data can directly use these buffers in session configure.
So, sending a proposal to mark xform as non-reusable till lifetime
of session. This will help PMDs to reduce session setup time.
Ayuj Verma (1):
lib/crypto: mark asym session-buffer non-reuseable
doc/guides/prog_guide/cryptodev_lib.rst | 6 ++++++
lib/librte_cryptodev/rte_cryptodev_pmd.h | 2 +-
2 files changed, 7 insertions(+), 1 deletion(-)
--
1.8.3.1
next reply other threads:[~2019-07-17 12:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-17 12:34 Ayuj Verma [this message]
2019-07-17 12:34 ` [dpdk-dev] [RFC] lib/crypto: " Ayuj Verma
2019-07-17 14:03 ` Trahe, Fiona
2019-07-17 14:10 ` Kusztal, ArkadiuszX
2019-07-18 9:56 ` Ayuj Verma
2019-07-18 10:49 ` Ayuj Verma
2019-07-17 14:10 ` [dpdk-dev] [RFC] " Kusztal, ArkadiuszX
2019-07-18 9:47 ` Ayuj Verma
2019-07-19 14:50 ` Ayuj Verma
2019-07-19 15:38 ` 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=1563366852-23118-1-git-send-email-ayverma@marvell.com \
--to=ayverma@marvell.com \
--cc=akhil.goyal@nxp.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--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).