From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by dpdk.org (Postfix) with ESMTP id 5F0E91C69F for ; Fri, 11 May 2018 15:36:36 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 May 2018 06:36:35 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,388,1520924400"; d="scan'208";a="57810884" Received: from pgsmsx112.gar.corp.intel.com ([10.108.55.201]) by orsmga002.jf.intel.com with ESMTP; 11 May 2018 06:36:31 -0700 Received: from pgsmsx102.gar.corp.intel.com ([169.254.6.245]) by PGSMSX112.gar.corp.intel.com ([169.254.3.57]) with mapi id 14.03.0319.002; Fri, 11 May 2018 21:36:30 +0800 From: "Gujjar, Abhinandan S" To: Akhil Goyal , "jerin.jacob@caviumnetworks.com" , "hemant.agrawal@nxp.com" , "dev@dpdk.org" CC: "De Lara Guarch, Pablo" , "Doherty, Declan" , "Vangati, Narender" , "Rao, Nikhil" Thread-Topic: [dpdk-dev, v1, 5/5] doc: add event crypto adapter documentation Thread-Index: AQHT1ZIGsVfpe1Z3IEG917K+JleWcKQqrSkA Date: Fri, 11 May 2018 13:36:29 +0000 Message-ID: <5612CB344B05EE4F95FC5B729939F78070705593@PGSMSX102.gar.corp.intel.com> References: <1522825047-61743-1-git-send-email-abhinandan.gujjar@intel.com> <3f456621-ff31-ced8-f399-7e19e01ffdf3@nxp.com> In-Reply-To: <3f456621-ff31-ced8-f399-7e19e01ffdf3@nxp.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNmQ5MzMzNWUtZjU3Ny00YWYxLWE0ZTktZjQ4MWZiZjI1NjJlIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoia2dyK0V0RmtiYXNMeUpOQWZyeTVKZFJrZmN2VDVyd1p0a21jc1dnWGtTanVzQ2VTa1NVOUg2ckZwbDZPd1h6aCJ9 dlp-product: dlpe-windows dlp-version: 11.0.200.100 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] [dpdk-dev, v1, 5/5] doc: add event crypto adapter documentation 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: Fri, 11 May 2018 13:36:36 -0000 Hi Akhil, > -----Original Message----- > From: Akhil Goyal > Sent: Monday, April 16, 2018 8:18 PM > To: Gujjar, Abhinandan S ; > jerin.jacob@caviumnetworks.com; hemant.agrawal@nxp.com; > dev@dpdk.org > Cc: De Lara Guarch, Pablo ; Doherty, > Declan ; Vangati, Narender > ; Rao, Nikhil > Subject: Re: [dpdk-dev, v1, 5/5] doc: add event crypto adapter > documentation >=20 > Hi Abhinandan, >=20 > On 4/4/2018 12:27 PM, Abhinandan Gujjar wrote: > > Add entries in the programmer's guide, API index, maintainer's file > > and release notes for the event crypto adapter. > > > > Signed-off-by: Abhinandan Gujjar > > --- >=20 > [.snip.] > > + > > +Set event request/response information > > +-------------------------------------- > > + > > +In the ENQ_DEQ mode, the application needs to specify the cryptodev > > +ID and queue pair ID (request information) in addition to the event > > +information (response information) needed to enqueue an event after > > +the crypto operation has completed. The request and response > > +information are specified in the ``struct rte_crypto_op`` private > > +data or session's private data. > > + > > +In the DEQ mode, the application is required to provide only the > > +response information. > > + > > +The SW adapter or HW PMD uses ``rte_crypto_op::sess_type`` to decide > > +whether request/response data is located in the crypto session/ > > +crypto security session or at an offset in the ``struct rte_crypto_op`= `. > > +The ``rte_crypto_op::private_data_offset`` is used to locate the > > +request/ response in the ``rte_crypto_op``. > > + > > +For crypto session, ``rte_cryptodev_sym_session_set_private_data()`` > > +API will be used to set request/response data. The same data will be > > +obtained by ``rte_cryptodev_sym_session_get_private_data()`` API. > > + > > +For security session, ``rte_security_session_set_private_data()`` API > > +will be used to set request/response data. The same data will be > > +obtained by ``rte_security_session_get_private_data()`` API. >=20 > I think you have missed this security API in your patches. > Also I don't think this methodology for adding the private data in sessio= n will > work in case of security sessions. As we have only one API for > creating/configuring the security session. However, we can add a paramete= r > in the rte_security_session_create(). Since this API is still experimenta= l, we > can change the parameters. What Say? Sorry for the delayed response. If you feel, changing the create API is the right approach please go ahead. We don't have strong opinion on this. Regards Abhinandan >=20 >=20 > -Akhil