From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 6E67F8E01 for ; Tue, 13 Feb 2018 17:11:13 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Feb 2018 08:11:12 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.46,507,1511856000"; d="scan'208";a="31084187" Received: from pgsmsx107.gar.corp.intel.com ([10.221.44.105]) by orsmga001.jf.intel.com with ESMTP; 13 Feb 2018 08:11:11 -0800 Received: from pgsmsx102.gar.corp.intel.com ([169.254.6.149]) by PGSMSX107.gar.corp.intel.com ([169.254.7.129]) with mapi id 14.03.0319.002; Wed, 14 Feb 2018 00:11:10 +0800 From: "Gujjar, Abhinandan S" To: "De Lara Guarch, Pablo" , "Doherty, Declan" , "akhil.goyal@nxp.com" , "Jerin.JacobKollanukkaran@cavium.com" CC: "dev@dpdk.org" , "Vangati, Narender" , "Rao, Nikhil" Thread-Topic: [RFC v3, 2/3] cryptodev: add support to set session private data Thread-Index: AQHTmz9Petu6K0PrfEuA5JGcYkmyuqOh+RoAgACavCA= Date: Tue, 13 Feb 2018 16:11:10 +0000 Message-ID: <5612CB344B05EE4F95FC5B729939F7807063A782@PGSMSX102.gar.corp.intel.com> References: <1517477426-169249-1-git-send-email-abhinandan.gujjar@intel.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYmZiMGZlZTgtYTEyNS00NzZkLWJjYjAtZWMxNmI4M2JkNDMxIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6ImZCeWxoZXMyUXBIam5hSDB0OXNPMWF1ZmRtNFwvYlM3cVwvQk84TE5cL3RXaE09In0= dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [172.30.20.205] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [RFC v3, 2/3] cryptodev: add support to set session private data X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Feb 2018 16:11:13 -0000 Hi Pablo, > -----Original Message----- > From: De Lara Guarch, Pablo > Sent: Tuesday, February 13, 2018 8:27 PM > To: Gujjar, Abhinandan S ; Doherty, Declan > ; akhil.goyal@nxp.com; > Jerin.JacobKollanukkaran@cavium.com > Cc: dev@dpdk.org; Vangati, Narender ; Rao, > Nikhil > Subject: RE: [RFC v3, 2/3] cryptodev: add support to set session private = data >=20 > Hi, >=20 > > -----Original Message----- > > From: Gujjar, Abhinandan S > > Sent: Thursday, February 1, 2018 9:30 AM > > To: Doherty, Declan ; akhil.goyal@nxp.com; > > De Lara Guarch, Pablo ; > > Jerin.JacobKollanukkaran@cavium.com > > Cc: dev@dpdk.org; Vangati, Narender ; > > Gujjar, Abhinandan S ; Rao, Nikhil > > > > Subject: [RFC v3, 2/3] cryptodev: add support to set session private > > data > > > > The application may want to store private data along with the > > rte_cryptodev that is transparent to the rte_cryptodev layer. > > For e.g., If an eventdev based application is submitting a > > rte_cryptodev_sym_session operation and wants to indicate event > > information required to construct a new event that will be enqueued to > > eventdev after completion of the rte_cryptodev_sym_session operation. > > This patch provides a mechanism for the application to associate this > > information with the rte_cryptodev_sym_session session. > > The application can set the private data using > > rte_cryptodev_sym_session_set_private_data() and retrieve it using > > rte_cryptodev_sym_session_get_private_data(). > > > > Signed-off-by: Abhinandan Gujjar > > Signed-off-by: Nikhil Rao >=20 > This looks good to me. I am expecting then a v1 with the implementation o= f > these functions. Sure. I will post the implementation. Thanks Abhinandan >=20 > Thanks, > Pablo