Hi Arek,
Please see inline. Thanks and regards Ayuj Verma ________________________________ From: Kusztal, ArkadiuszX <arkadiuszx.kusz...@intel.com> Sent: 17 July 2019 19:40 To: Ayuj Verma; akhil.go...@nxp.com Cc: Trahe, Fiona; Shally Verma; Sunila Sahu; Kanaka Durga Kotamarthy; dev@dpdk.org Subject: RE: [RFC] mark asym session-buffer non-reuseable Hi Ayuj, > -----Original Message----- > From: Ayuj Verma [mailto:ayve...@marvell.com] > Sent: Wednesday, July 17, 2019 2:34 PM > To: akhil.go...@nxp.com > Cc: Kusztal, ArkadiuszX <arkadiuszx.kusz...@intel.com>; Trahe, Fiona > <fiona.tr...@intel.com>; shal...@marvell.com; ss...@marvell.com; > kkotamar...@marvell.com; dev@dpdk.org; Ayuj Verma > <ayve...@marvell.com> > Subject: [RFC] mark asym session-buffer non-reuseable > > 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, [AK] - what is you expected session lifetime? (2,3,50 packets?) [Ayuj] In practical scenario like SSL, handshake will happen in some 10-15 packets. > 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
