From mboxrd@z Thu Jan 1 00:00:00 1970 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) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 8F4A5219EF; Fri, 9 Mar 2018 17:36:00 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Fri, 09 Mar 2018 17:36:00 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=ZCd1dg0C+FNKtBB/aCFyc/kvM2 ZD5QQ2/LCE3Twazzc=; b=Dqa0EmYs8urIfzgbOY2C/4/3909cY+DxeEbIr16xAH QbYNAEpod9WH3sBCaojVx8w7EWtbT9VpD1WJxwiew9fFBFCufg06qMFCwTjQF9EU BHd3a3q/pNqFrN9vMl7xvkvlRPI/pKkE9+5Syu5XyOmhCxwwk11QvI9kDnzeh0lQ E= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=ZCd1dg 0C+FNKtBB/aCFyc/kvM2ZD5QQ2/LCE3Twazzc=; b=fCiVS8XriZXNsZNI40kBKP Qjas+cuw9nXcGWxVLukEyCDlciH3EAZc5KTBdikexTMousp5zbf5thatA6Cu/CnJ 2IWn3AhYxc5zQaF3KU7KZ4t/23PjL/mveFdrXCuDTtw7+CqRM1YNHrx8bTfk/Jbg 2CKuA8hv3du2p4EvV5ETfWEa22itTYyhMw91RosMm3CWu6GiBjW20hY/ViIeB229 gxWSrdWxTOWRHJFaGpwJB1R59yZQsC0pnVIzzAbrFsgbRl9/v8nU2VGdzF16Xq4n SKtM/MOi45bCiuvu65ZdHLAtWbqNIqTFUcOvruY+LGSgtkMs7sRoWBVIaWZu3SBA == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id D7750240CE; Fri, 9 Mar 2018 17:35:59 -0500 (EST) From: Thomas Monjalon To: "Luse, Paul E" Cc: dev@dpdk.org, pablo.de.lara.guarch@intel.com, declan.doherty@intel.com Date: Fri, 09 Mar 2018 23:35:45 +0100 Message-ID: <6138797.4gfP7HpVFi@xps> In-Reply-To: <82C9F782B054C94B9FC04A331649C77AA6ABA2B4@fmsmsx104.amr.corp.intel.com> References: <82C9F782B054C94B9FC04A331649C77AA6ABA2B4@fmsmsx104.amr.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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: Fri, 09 Mar 2018 22:36:04 -0000 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