From: Shally Verma <shallyv@marvell.com>
To: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "akhil.goyal@nxp.com" <akhil.goyal@nxp.com>,
"Trahe, Fiona" <fiona.trahe@intel.com>,
"shally.verma@caviumnetworks.com"
<shally.verma@caviumnetworks.com>
Subject: Re: [dpdk-dev] [EXT] [PATCH] cryptodev: extend api of asymmetric crypto by sessionless
Date: Fri, 14 Jun 2019 11:23:07 +0000 [thread overview]
Message-ID: <BN6PR1801MB20521D06B16E55BA24E4753FADEE0@BN6PR1801MB2052.namprd18.prod.outlook.com> (raw)
In-Reply-To: <06EE24DD0B19E248B53F6DC8657831551B2687D0@hasmsx109.ger.corp.intel.com>
> -----Original Message-----
> From: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>
> Sent: Friday, June 14, 2019 3:55 PM
> To: Shally Verma <shallyv@marvell.com>; dev@dpdk.org
> Cc: akhil.goyal@nxp.com; Trahe, Fiona <fiona.trahe@intel.com>;
> shally.verma@caviumnetworks.com
> Subject: RE: [EXT] [PATCH] cryptodev: extend api of asymmetric crypto by
> sessionless
>
...
> > > [Shally] Ack to this change. But is this all that is needed to
> > > support sessionless? Do you have working poc with sessionless?
> > >
> >
> > [AK]
> > xform holds to get working. Crypto_op holds sess_type From our side
> > for now we not intend to store any user information in session at all.
> > For sure not private keys, any other information is small enough
> > comparing to asymmetric crypto computation time that it has no gain to
> > allocate session for it.
> >
> [AK] Sorry, I had to fix bad writing.
> rte_crypto_asym_xform holds enough information, and rte_crypto_op holds
> sess_type.
Can you submit example app working on sessionless ?
> >
> > > Thanks
> > > Shally
> > >
> > > >
> > > > __extension__
> > > > union {
> > > > --
> > > > 2.7.4
next prev parent reply other threads:[~2019-06-14 11:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-03 19:44 [dpdk-dev] " Arek Kusztal
2019-06-05 12:16 ` [dpdk-dev] [EXT] " Shally Verma
2019-06-14 10:21 ` Kusztal, ArkadiuszX
2019-06-14 10:24 ` Kusztal, ArkadiuszX
2019-06-14 11:23 ` Shally Verma [this message]
2019-06-14 12:12 ` Kusztal, ArkadiuszX
2019-06-20 14:17 ` [dpdk-dev] " Akhil Goyal
2019-06-21 11:58 ` Trahe, Fiona
2019-06-21 12:22 ` Akhil Goyal
2019-06-21 14:18 ` Trahe, Fiona
2019-06-24 7:05 ` Akhil Goyal
2019-06-27 11:54 ` Trahe, Fiona
2019-06-28 16:10 ` Shally Verma
2019-06-28 17:27 ` Trahe, Fiona
2019-06-30 8:37 ` Shally Verma
2019-08-12 9:26 ` [dpdk-dev] [EXT] " Anoob Joseph
2019-08-12 10:00 ` Kusztal, ArkadiuszX
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=BN6PR1801MB20521D06B16E55BA24E4753FADEE0@BN6PR1801MB2052.namprd18.prod.outlook.com \
--to=shallyv@marvell.com \
--cc=akhil.goyal@nxp.com \
--cc=arkadiuszx.kusztal@intel.com \
--cc=dev@dpdk.org \
--cc=fiona.trahe@intel.com \
--cc=shally.verma@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).