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 BE792A328D for ; Wed, 23 Oct 2019 08:23:36 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 989171BF8F; Wed, 23 Oct 2019 08:23:36 +0200 (CEST) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) by dpdk.org (Postfix) with ESMTP id C98601BF8F for ; Wed, 23 Oct 2019 08:23:34 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 4A53121D51; Wed, 23 Oct 2019 02:23:34 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 23 Oct 2019 02:23:34 -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=bNU3A80PW3vLqs4abuWBU2zntLje2WczeDTlmds2Ni8=; b=hNNBoN8B7A8C nV1dH8ipyQnBTdQrhGBnwm7cSQneIqkD6uQpSO/4MzPz/mBEA6FMMOvzXPlv+8A2 3dyMVs4dfV+nEJnGp1LQFPOdliLKtkqbh4z2/vUwUj2Xgxs3LwVSq9EtKhQ2dpvK w1Cx9sNQaQgN1k+3sPrEjXirKNfrlGc= 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=bNU3A80PW3vLqs4abuWBU2zntLje2WczeDTlmds2N i8=; b=cxGL5brznN4u3uYhm0zvJAF0K9ehunKRgj2vrlUJgMhfum/t8XODrPwa4 74pMFEFVs7rB0vZigPDlzUXzIJGDq0U7rSrp4r+8gqup/rqll3scZpsTLr0il3tu pbHyl6/Nt6JFWjlkjgbGAnugoVL3a1zkduMFca0W9NLITzEsphSg8t2u4QjXEwsa U91UVnLO5Wf6gM50uulY/+3F3lg5gDJBzfRn6Ba6a4ppzssLZtjQLUoZ3s4E9UyR 1SG1KMle0hryGJPaLavJY62hiECIov2gRhHmAc/hYs5bIdKmGb64Ac3EeW6wp1BO I7mAtwwOZWO5fY+F6/4PMm7bDogoA== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrkeekgddutdehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecukf hppeejjedrudefgedrvddtfedrudekgeenucfrrghrrghmpehmrghilhhfrhhomhepthhh ohhmrghssehmohhnjhgrlhhonhdrnhgvthenucevlhhushhtvghrufhiiigvpedt 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 3951B80060; Wed, 23 Oct 2019 02:23:32 -0400 (EDT) From: Thomas Monjalon To: Jerin Jacob Cc: Honnappa Nagarahalli , dpdk-dev , "Akhil.goyal@nxp.com" , "hemant.agrawal@nxp.com" , "anoobj@marvell.com" , "pathreya@marvell.com" , "pkapoor@marvell.com" , "jerinj@marvell.com" , nd Date: Wed, 23 Oct 2019 08:23:31 +0200 Message-ID: <3373803.DCgnikpo0B@xps> In-Reply-To: References: <20191012073421.44748-1-jerinj@marvell.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] maintainers: update for armv8 crypto library 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" 23/10/2019 04:50, Jerin Jacob: > In past, there was a concern with this approach about maintaining the > assembly code in dpdk.org. Is this concern still valid? [...] > DPDK does not define any such interface. It was pushed to external library > for the reason mentioned above. Yes it is questionable to host some asm code which is doing a processing not really specific to DPDK. Also, my first thought was that this library could be used by other projects. Another concern about integrating this crypto lib in DPDK is to know whether it would have an impact on DPDK packaging and delivering? I don't remember any answer about legal export of this crypto processing.