From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: Question on AESNI PMD Date: Fri, 09 Mar 2018 23:35:45 +0100 Message-ID: <6138797.4gfP7HpVFi@xps> References: <82C9F782B054C94B9FC04A331649C77AA6ABA2B4@fmsmsx104.amr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, pablo.de.lara.guarch@intel.com, declan.doherty@intel.com To: "Luse, Paul E" Return-path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id D5A9C5F16 for ; Fri, 9 Mar 2018 23:36:03 +0100 (CET) In-Reply-To: <82C9F782B054C94B9FC04A331649C77AA6ABA2B4@fmsmsx104.amr.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" Cc Declan and Pablo, the maintainers 09/03/2018 23:08, Luse, Paul E: > Hi, > > I'm working on an SPDK module that uses the DPDK cryptodev framework, initially 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. > > 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. > > 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