From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 093535F1D for ; Tue, 13 Mar 2018 15:16:25 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Mar 2018 07:16:24 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.47,465,1515484800"; d="scan'208";a="41576817" Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201]) by orsmga002.jf.intel.com with ESMTP; 13 Mar 2018 07:16:24 -0700 Received: from FMSMSX110.amr.corp.intel.com (10.18.116.10) by FMSMSX103.amr.corp.intel.com (10.18.124.201) with Microsoft SMTP Server (TLS) id 14.3.319.2; Tue, 13 Mar 2018 07:16:24 -0700 Received: from fmsmsx104.amr.corp.intel.com ([169.254.3.244]) by FMSMSX110.amr.corp.intel.com ([169.254.14.108]) with mapi id 14.03.0319.002; Tue, 13 Mar 2018 07:16:24 -0700 From: "Luse, Paul E" To: Thomas Monjalon CC: "dev@dpdk.org" , "De Lara Guarch, Pablo" , "Doherty, Declan" Thread-Topic: [dpdk-dev] Question on AESNI PMD Thread-Index: AdO38lpOBr50FV93SX6Y0kvlI3FInQAAM7ZgABG24YAApu/YwA== Date: Tue, 13 Mar 2018 14:16:23 +0000 Message-ID: <82C9F782B054C94B9FC04A331649C77AA6ABEFF1@fmsmsx104.amr.corp.intel.com> References: <82C9F782B054C94B9FC04A331649C77AA6ABA2B4@fmsmsx104.amr.corp.intel.com> <6138797.4gfP7HpVFi@xps> In-Reply-To: <6138797.4gfP7HpVFi@xps> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZjA5Y2FlNzEtM2E0NC00MDY3LTg1YmQtNDA1NjI5NTlkMGY3IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjIuNS4xOCIsIlRydXN0ZWRMYWJlbEhhc2giOiJ1OW1qZDlUTjZhemM3Rks0d2ZIMlwvUHgwOHpIZ01WTUdTdGpZR0tSREt5RHI3V2RWb0dqXC9JR00xZUJocE1lNEwifQ== x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [10.1.200.107] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] Question on AESNI PMD 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 Mar 2018 14:16:26 -0000 Any thoughts on this? Thanks, Paul -----Original Message----- From: Thomas Monjalon [mailto:thomas@monjalon.net]=20 Sent: Friday, March 9, 2018 3:36 PM To: Luse, Paul E Cc: dev@dpdk.org; De Lara Guarch, Pablo ; D= oherty, Declan Subject: Re: [dpdk-dev] Question on AESNI PMD Cc Declan and Pablo, the maintainers 09/03/2018 23:08, Luse, Paul E: > Hi, >=20 > I'm working on an SPDK module that uses the DPDK cryptodev framework, ini= tially I'm using the AESNI PMD and have a few questions. in the doc it says= that only in-place is supported however I see code in set_mb_job_params() = just after the comment "Mutable crypto operation parameters" it appears to = support a separate src and dst m_buf so curious about that. >=20 > For my use case (storage) I'm using external data buffers so I can't use = that code anyways but I was able to make some minor changes and am able to = pass in different src and dst m_bufs that point to my own data buffers (not= in the packet) and it seems to be working fine. >=20 > So my 2 questions are: >=20 > (1) is the documented in-place limitation simply not correct? >=20 > (2) would there be any upstream interest in supporting a patch that enabl= es m_bufs using external data buffers for src and dst? >=20 > Thanks! > Paul