From: "Trahe, Fiona" <fiona.trahe@intel.com> To: Ayuj Verma <ayverma@marvell.com>, "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>, "akhil.goyal@nxp.com" <akhil.goyal@nxp.com> Cc: Shally Verma <shallyv@marvell.com>, Sunila Sahu <ssahu@marvell.com>, Kanaka Durga Kotamarthy <kkotamarthy@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>, "Trahe, Fiona" <fiona.trahe@intel.com> Subject: Re: [dpdk-dev] [RFC] mark asym session-buffer non-reuseable Date: Fri, 19 Jul 2019 15:38:12 +0000 Message-ID: <348A99DA5F5B7549AA880327E580B435897C97E6@IRSMSX101.ger.corp.intel.com> (raw) In-Reply-To: <MN2PR18MB25420DEADF7CF2612553813EADCB0@MN2PR18MB2542.namprd18.prod.outlook.com> No need as API is still experimental. Howver I'd suggest changing the subject to "declare crypto asym xform immutable" non-reusable is confusing as the session and xform will be re-used on all the ops associated with the session. From: Ayuj Verma [mailto:ayverma@marvell.com] Sent: Friday, July 19, 2019 3:51 PM To: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com>; akhil.goyal@nxp.com Cc: Trahe, Fiona <fiona.trahe@intel.com>; Shally Verma <shallyv@marvell.com>; Sunila Sahu <ssahu@marvell.com>; Kanaka Durga Kotamarthy <kkotamarthy@marvell.com>; dev@dpdk.org Subject: Re: [RFC] mark asym session-buffer non-reuseable Hi Akhil, Arek, Fiona, Since this require changes in other Asym PMD( qat) apart from openssl (we plan to send changes for this), so should we need to send any announcement on ABI breakage here before proposing patch v1? Thanks and regards Ayuj Verma ________________________________ From: Ayuj Verma Sent: 18 July 2019 15:17:54 To: Kusztal, ArkadiuszX; akhil.goyal@nxp.com<mailto:akhil.goyal@nxp.com> Cc: Trahe, Fiona; Shally Verma; Sunila Sahu; Kanaka Durga Kotamarthy; dev@dpdk.org<mailto:dev@dpdk.org> Subject: Re: [RFC] mark asym session-buffer non-reuseable Hi Arek, Please see inline. Thanks and regards Ayuj Verma ________________________________ From: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com<mailto:arkadiuszx.kusztal@intel.com>> Sent: 17 July 2019 19:40 To: Ayuj Verma; akhil.goyal@nxp.com<mailto:akhil.goyal@nxp.com> Cc: Trahe, Fiona; Shally Verma; Sunila Sahu; Kanaka Durga Kotamarthy; dev@dpdk.org<mailto:dev@dpdk.org> Subject: RE: [RFC] mark asym session-buffer non-reuseable Hi Ayuj, > -----Original Message----- > From: Ayuj Verma [mailto:ayverma@marvell.com] > Sent: Wednesday, July 17, 2019 2:34 PM > To: akhil.goyal@nxp.com<mailto:akhil.goyal@nxp.com> > Cc: Kusztal, ArkadiuszX <arkadiuszx.kusztal@intel.com<mailto:arkadiuszx.kusztal@intel.com>>; Trahe, Fiona > <fiona.trahe@intel.com<mailto:fiona.trahe@intel.com>>; shallyv@marvell.com<mailto:shallyv@marvell.com>; ssahu@marvell.com<mailto:ssahu@marvell.com>; > kkotamarthy@marvell.com<mailto:kkotamarthy@marvell.com>; dev@dpdk.org<mailto:dev@dpdk.org>; Ayuj Verma > <ayverma@marvell.com<mailto:ayverma@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
prev parent reply index Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-07-17 12:34 Ayuj Verma 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 [this message]
Reply instructions: You may reply publically 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=348A99DA5F5B7549AA880327E580B435897C97E6@IRSMSX101.ger.corp.intel.com \ --to=fiona.trahe@intel.com \ --cc=akhil.goyal@nxp.com \ --cc=arkadiuszx.kusztal@intel.com \ --cc=ayverma@marvell.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
DPDK-dev Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/dpdk-dev/0 dpdk-dev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 dpdk-dev dpdk-dev/ https://lore.kernel.org/dpdk-dev \ dev@dpdk.org public-inbox-index dpdk-dev Example config snippet for mirrors Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.dpdk.dev AGPL code for this site: git clone https://public-inbox.org/public-inbox.git