From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jerin Jacob Subject: Re: [v3,1/5] eventdev: introduce event crypto adapter Date: Tue, 8 May 2018 18:19:19 +0530 Message-ID: <20180508124918.GA2393@jerin> References: <1525546030-11204-1-git-send-email-abhinandan.gujjar@intel.com> <1525546030-11204-2-git-send-email-abhinandan.gujjar@intel.com> <20180507093516.GA8052@jerin> <5612CB344B05EE4F95FC5B729939F78070703554@PGSMSX102.gar.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Akhil Goyal , "hemant.agrawal@nxp.com" , "dev@dpdk.org" , "Vangati, Narender" , "Rao, Nikhil" , "Eads, Gage" To: "Gujjar, Abhinandan S" Return-path: Received: from NAM01-SN1-obe.outbound.protection.outlook.com (mail-sn1nam01on0060.outbound.protection.outlook.com [104.47.32.60]) by dpdk.org (Postfix) with ESMTP id 9DB1B8DA4 for ; Tue, 8 May 2018 14:49:40 +0200 (CEST) Content-Disposition: inline In-Reply-To: <5612CB344B05EE4F95FC5B729939F78070703554@PGSMSX102.gar.corp.intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" -----Original Message----- > Date: Tue, 8 May 2018 07:34:52 +0000 > From: "Gujjar, Abhinandan S" > To: Akhil Goyal , Jerin Jacob > > CC: "hemant.agrawal@nxp.com" , "dev@dpdk.org" > , "Vangati, Narender" , "Rao, > Nikhil" , "Eads, Gage" > Subject: RE: [dpdk-dev] [v3,1/5] eventdev: introduce event crypto adapter > > Hi Akhil, > > Thanks for the feedback on the diagram. My thoughts are also in line with diagram. > In fact, my diagram also depicts same. The only difference is that, you have shown application in a separate block. > The "crypto stage + enqueue to cryptodev" block itself is part of an application. > So, for more clarity, I will add "application" as additional text to the block. > With the limited time, changing diagram needs change in SVG file as well. > In case, if you still feel there a change required we can take it up later. IMO, At least in the header file you can copy the proposed and agreed diagram. if you don't have time then documentation patch we can fix it just after the initial patch and worst case apply the documentation patch after RC3.