From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id F02FB6D45 for ; Mon, 11 Sep 2017 11:39:10 +0200 (CEST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 Sep 2017 02:39:10 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.42,377,1500966000"; d="scan'208";a="133975967" Received: from irsmsx106.ger.corp.intel.com ([163.33.3.31]) by orsmga002.jf.intel.com with ESMTP; 11 Sep 2017 02:39:09 -0700 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.167]) by IRSMSX106.ger.corp.intel.com ([169.254.8.36]) with mapi id 14.03.0319.002; Mon, 11 Sep 2017 10:39:08 +0100 From: "De Lara Guarch, Pablo" To: "Zhang, Roy Fan" CC: "dev@dpdk.org" Thread-Topic: [PATCH v2 0/8] Remove temporary digest allocation Thread-Index: AQHTJjCM2CNd9xzQpU6GQiXpbUROxKKmKrsAgAlERUA= Date: Mon, 11 Sep 2017 09:39:08 +0000 Message-ID: References: <20170818072103.1416-1-pablo.de.lara.guarch@intel.com> <20170905022007.55749-1-pablo.de.lara.guarch@intel.com> <9F7182E3F746AB4EA17801C148F3C60433038C6F@IRSMSX101.ger.corp.intel.com> In-Reply-To: <9F7182E3F746AB4EA17801C148F3C60433038C6F@IRSMSX101.ger.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNTk2ODQ2YjYtOTNjMC00ZmY3LWJhZmMtMDc2MjM4YjgxZDE1IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6Im9ER1wvVEl5aEcyeEVnbk1CR3BpVDE1XC9pYWp3T2RHS2Z1Z01pUzhST0J5VT0ifQ== x-ctpclassification: CTP_IC dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [163.33.239.181] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v2 0/8] Remove temporary digest allocation 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: Mon, 11 Sep 2017 09:39:11 -0000 > -----Original Message----- > From: Zhang, Roy Fan > Sent: Tuesday, September 5, 2017 1:39 PM > To: De Lara Guarch, Pablo > Cc: dev@dpdk.org > Subject: RE: [PATCH v2 0/8] Remove temporary digest allocation >=20 > Hi Pablo, >=20 > Thanks, looks great! >=20 > Regards, > Fan >=20 > > -----Original Message----- > > From: De Lara Guarch, Pablo > > Sent: Tuesday, September 5, 2017 3:20 AM > > To: Doherty, Declan ; Zhang, Roy Fan > > ; jerin.jacob@caviumnetworks.com > > Cc: dev@dpdk.org; De Lara Guarch, Pablo > > > > Subject: [PATCH v2 0/8] Remove temporary digest allocation > > > > When performing authentication verification, some crypto PMDs require > > extra memory where the generated digest can be placed. > > Currently, these PMDs are getting the memory from the end of the > > source mbuf, which might fail if there is not enough tailroom. > > > > To avoid this situation, some memory is allocated in each queue pair > > of the device, to store temporarily these digests. > > > > Changes in v2: > > - Removed incorrect indirection when getting the memory > > to store the generated digest (i.e. removed "&" in &temp_digest) >=20 > Series Acked-by: Fan Zhang Applied to dpdk-next-crypto. Pablo