> -----Original Message-----
> From: Shally Verma [mailto:shal...@marvell.com]
> Sent: Friday, June 14, 2019 1:23 PM
> To: Kusztal, ArkadiuszX <arkadiuszx.kusz...@intel.com>; dev@dpdk.org
> Cc: akhil.go...@nxp.com; Trahe, Fiona <fiona.tr...@intel.com>;
> shally.ve...@caviumnetworks.com
> Subject: RE: [EXT] [PATCH] cryptodev: extend api of asymmetric crypto by
> sessionless
>
>
>
> > -----Original Message-----
> > From: Kusztal, ArkadiuszX <arkadiuszx.kusz...@intel.com>
> > Sent: Friday, June 14, 2019 3:55 PM
> > To: Shally Verma <shal...@marvell.com>; dev@dpdk.org
> > Cc: akhil.go...@nxp.com; Trahe, Fiona <fiona.tr...@intel.com>;
> > shally.ve...@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 ?
[AK] Sure, I will.
>
> > >
> > > > Thanks
> > > > Shally
> > > >
> > > > >
> > > > > __extension__
> > > > > union {
> > > > > --
> > > > > 2.7.4
