From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 0130FA328D for ; Wed, 23 Oct 2019 08:40:18 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id A13F91BFA1; Wed, 23 Oct 2019 08:40:17 +0200 (CEST) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id 3281C1BF7C for ; Wed, 23 Oct 2019 08:40:16 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id BD3A2220AB; Wed, 23 Oct 2019 02:40:15 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 23 Oct 2019 02:40:15 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=IiTxa9nGFGMRWaZj9voyXPQvEPU6sueEbOdeOagZQKU=; b=ObYTx/WgaaTO Ml8+Kflyhn0Api9jLn1iuE9Z6LCVVna4b+YTwp/SdzAoDHUGf5SPWpsStMtz/KBE BO1kPZKXYJbsYTNewex6wDM1N/Es8rfa77VNSk+7e90ZhR4zDEF6QMxZ1R/D0dfb 86wj6BTI9mez1qfj9fy+Ol2i1XAan+8= 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-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=IiTxa9nGFGMRWaZj9voyXPQvEPU6sueEbOdeOagZQ KU=; b=pIeMjEnXHUX+9rz2NZbgETuTw6xMCDq6F48SdCLCzbgVl8hZ4PBtwXhvq ZbxnfarExo1ssp+onEREp/KI/GSkCDpHYx+naJZt5tfmd/jSShV0W+WvUX3wQAQ6 kEB1MoKBHuUCB5W9G4FuPHx81WXIAWSrWWwEWvj4WtMOvoc8OEW/I6NJ2trpEBPe 2NOyR8bMIxML5MHHgA4WNxUIlqomB+byalmr9i0lNlQCuF9DI1vTih6ObISFPe+R Mo4r2C6SLrKQ/sZU7Rq+IE3HHaVL+gyMYuvRwqLb3wZYZJadaWlIbp6UxR5MgxTV /4v5iYN74xVg5H9gq5mpF9VqbXu4w== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrkeekgddutdekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf hppeejjedrudefgedrvddtfedrudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhh ohhmrghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedu X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 70B5180059; Wed, 23 Oct 2019 02:40:14 -0400 (EDT) From: Thomas Monjalon To: Honnappa Nagarahalli Cc: "Akhil.goyal@nxp.com" , "dev@dpdk.org" , "hemant.agrawal@nxp.com" , "jerinj@marvell.com" , nd Date: Wed, 23 Oct 2019 08:40:13 +0200 Message-ID: <3296022.lNpl9XSYZE@xps> In-Reply-To: References: MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] Armv8_crypto PMD future. 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 22/10/2019 22:19, Honnappa Nagarahalli: > From: Akhil Goyal > > We can have 2 possible solutions to this situation > > > > 1. Arm host it somewhere and let people contribute to that. > > 2. Integrate it inside DPDK repo. > > [Honnappa] I don't have any issues with the 2nd option. So you want this code to be part of the PMD? You think no other project would like to use such crypto code? What are the export restrictions for this code?