From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by dpdk.org (Postfix) with ESMTP id C4E1E10D06; Thu, 30 Mar 2017 15:24:21 +0200 (CEST) Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by orsmga104.jf.intel.com with ESMTP; 30 Mar 2017 06:24:20 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.36,246,1486454400"; d="scan'208";a="82710105" Received: from irsmsx152.ger.corp.intel.com ([163.33.192.66]) by fmsmga006.fm.intel.com with ESMTP; 30 Mar 2017 06:24:19 -0700 Received: from irsmsx156.ger.corp.intel.com (10.108.20.68) by IRSMSX152.ger.corp.intel.com (163.33.192.66) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 30 Mar 2017 14:24:19 +0100 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.239]) by IRSMSX156.ger.corp.intel.com ([169.254.3.246]) with mapi id 14.03.0319.002; Thu, 30 Mar 2017 14:24:18 +0100 From: "De Lara Guarch, Pablo" To: "Doherty, Declan" , "Gonzalez Monroy, Sergio" , "dev@dpdk.org" CC: "stable@dpdk.org" Thread-Topic: [PATCH] crypto/aesni_gcm: do crypto op in dequeue function Thread-Index: AQHSqJJlcKJcgPVZz06SCxxkLUpnQ6GtNDGAgAAp/tA= Date: Thu, 30 Mar 2017 13:24:17 +0000 Message-ID: References: <20170329134253.31909-1-sergio.gonzalez.monroy@intel.com> <7923ff78-ba53-4573-5c83-efc699ff53c1@intel.com> In-Reply-To: <7923ff78-ba53-4573-5c83-efc699ff53c1@intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZjg0OThkYjgtYzk0Yi00NzU2LWIwNzctMjUyODQyYTI3ZWE1IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IlZhaWJVbTZlWStrK2V5UXdvQkhZYlpReVwvZ2M2WEpncU5mMzVuUjdESk5jPSJ9 x-ctpclassification: CTP_IC x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-stable] [PATCH] crypto/aesni_gcm: do crypto op in dequeue function X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Mar 2017 13:24:22 -0000 > -----Original Message----- > From: Doherty, Declan > Sent: Thursday, March 30, 2017 12:45 PM > To: Gonzalez Monroy, Sergio; dev@dpdk.org > Cc: De Lara Guarch, Pablo; stable@dpdk.org > Subject: Re: [PATCH] crypto/aesni_gcm: do crypto op in dequeue function >=20 > On 29/03/17 14:42, Sergio Gonzalez Monroy wrote: > > There is bug when more crypto ops are enqueued than dequeued. > > The return value is not checked when trying to enqueue the > > processed crypto op into the internal ring, which in the case of being > > full will results in crypto ops and mbufs being leaked. > > The issue is more obvious with different cores doing enqueue/dequeue. > > > > This patch moves the crypto operation to the dequeue function which > > fixes the above issue without having to check for the number of free > > entries in the ring. > > > > Fixes: eec136f3c54f ("aesni_gcm: add driver for AES-GCM crypto > operations") > > > > Signed-off-by: Sergio Gonzalez Monroy > > > --- > ... > > >=20 > Hey Sergio, this looks good but it needs to be rebased for the rte_ring > API change. I also see a marginally performance increase with this > change using the crypto-perf app which wasn't expected. >=20 >=20 > Acked-by: Declan Doherty Applied to dpdk-next-crypto. Thanks, Pablo