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 019B95F5F for ; Fri, 9 Mar 2018 23:08:54 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Mar 2018 14:08:53 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.47,447,1515484800"; d="scan'208,217";a="23141440" Received: from fmsmsx103.amr.corp.intel.com ([10.18.124.201]) by fmsmga007.fm.intel.com with ESMTP; 09 Mar 2018 14:08:53 -0800 Received: from fmsmsx104.amr.corp.intel.com ([169.254.3.244]) by FMSMSX103.amr.corp.intel.com ([169.254.2.34]) with mapi id 14.03.0319.002; Fri, 9 Mar 2018 14:08:53 -0800 From: "Luse, Paul E" To: "dev@dpdk.org" Thread-Topic: Question on AESNI PMD Thread-Index: AdO38lpOBr50FV93SX6Y0kvlI3FInQAAM7Zg Date: Fri, 9 Mar 2018 22:08:52 +0000 Message-ID: <82C9F782B054C94B9FC04A331649C77AA6ABA2B4@fmsmsx104.amr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZjE3NDc5MzgtMTJhOS00MTZmLWFkZDgtN2I0NDJmNTk2YjMyIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjIuNS4xOCIsIlRydXN0ZWRMYWJlbEhhc2giOiJnOTZ5czVkVWxaNWY1M0ZTYlVNY2pjXC9paDRcL2QxSnVnSjc4S25aMmlFSHVWdXppU0p4WEtuU2JIMFppQms5eVoifQ== 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] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [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: Fri, 09 Mar 2018 22:08:55 -0000 Hi, I'm working on an SPDK module that uses the DPDK cryptodev framework, initi= ally I'm using the AESNI PMD and have a few questions. in the doc it says t= hat only in-place is supported however I see code in set_mb_job_params() ju= st after the comment "Mutable crypto operation parameters" it appears to su= pport a separate src and dst m_buf so curious about that. For my use case (storage) I'm using external data buffers so I can't use th= at code anyways but I was able to make some minor changes and am able to pa= ss in different src and dst m_bufs that point to my own data buffers (not i= n the packet) and it seems to be working fine. So my 2 questions are: (1) is the documented in-place limitation simply not correct? (2) would there be any upstream interest in supporting a patch that enables= m_bufs using external data buffers for src and dst? Thanks! Paul