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 7B633A3160 for ; Sat, 12 Oct 2019 09:34:50 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 9D7931EA2E; Sat, 12 Oct 2019 09:34:48 +0200 (CEST) Received: from mx0b-0016f401.pphosted.com (mx0a-0016f401.pphosted.com [67.231.148.174]) by dpdk.org (Postfix) with ESMTP id 894A61EA2D for ; Sat, 12 Oct 2019 09:34:47 +0200 (CEST) Received: from pps.filterd (m0045849.ppops.net [127.0.0.1]) by mx0a-0016f401.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id x9C7UHAa002153; Sat, 12 Oct 2019 00:34:42 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=marvell.com; h=from : to : cc : subject : date : message-id : mime-version : content-transfer-encoding : content-type; s=pfpt0818; bh=xd+PSoU35bL+X5szFVeFYc0HhMd9H8r86zpQK6NYEss=; b=fsxoUvYLCWNrU0fccZIf+3SJmqtfaqqhw5x8ZRIf5NxXPyhSkJJQnQEmS/zQV19w4W4T k47t9aHozkR/OImuEpouLPffAQWqjIo687tsX3sgpwOqSUz9drbOHb5ViYGFWHHtag22 gF/b2x1Gydy/E1OqHNC2uAePCconvqOoW2xRldJBvjkfXT3DSb6uYnjU2ze4ebKzTtd7 4AoFjy5kdhfD9qMVBcWuHKdrf+upIGQH82CAjgMIS9TG3mqZeqN5CpYsgBwvPe+5Hjeo XLPoK5iFzTQRZVF+llG0Ki2GpXSVCcG6vxRnqnVyrMKV1dFS/SvqQTuG60keFUKbGfSt Rw== Received: from sc-exch01.marvell.com ([199.233.58.181]) by mx0a-0016f401.pphosted.com with ESMTP id 2vjj6v554x-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Sat, 12 Oct 2019 00:34:42 -0700 Received: from SC-EXCH01.marvell.com (10.93.176.81) by SC-EXCH01.marvell.com (10.93.176.81) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Sat, 12 Oct 2019 00:34:41 -0700 Received: from maili.marvell.com (10.93.176.43) by SC-EXCH01.marvell.com (10.93.176.81) with Microsoft SMTP Server id 15.0.1367.3 via Frontend Transport; Sat, 12 Oct 2019 00:34:41 -0700 Received: from jerin-lab.marvell.com (jerin-lab.marvell.com [10.28.34.14]) by maili.marvell.com (Postfix) with ESMTP id AB82B3F703F; Sat, 12 Oct 2019 00:34:38 -0700 (PDT) From: To: CC: , , , , , , , Jerin Jacob Date: Sat, 12 Oct 2019 13:04:21 +0530 Message-ID: <20191012073421.44748-1-jerinj@marvell.com> X-Mailer: git-send-email 2.23.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,1.0.8 definitions=2019-10-12_03:2019-10-10,2019-10-12 signatures=0 Subject: [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" From: Jerin Jacob Update the armv8 crypto PMD maintainership. https://github.com/caviumnetworks/armv8_crypto external crypto the library will not be maintained and probably removed soon therefor updating the PMD documentation to reflect the same. Signed-off-by: Jerin Jacob --- This patch is based on the discussion of the following thread http://mails.dpdk.org/archives/dev/2019-October/146005.html In summary, # ARMv8 crypto PMD depends on an external library owned by Marvell, specifically crafted to the DPDK performance use case. # There is no upstream path to this library and it will not be maintained due to that fact that it a) Creates fragmentation of the SW b) Contribution policy concerning external Github Repos c) None other than Marvell can contribute to this library and this makes difficult for other stakeholder to use it. # As the maintainer, I would like to make forward progress by providing the following options. None of the options are converging as the result I would like to step down from the maintainership of the incomplete PMD as I don't see any options for collaboration, improvement in the library nor follows the open source philosophy in the way it is structured out now. option 1) Move external library(BSD-3 license) to dpdk.org so that every armv8 vendors can contribute, improve and avoid SW fragmentation and therefore better quality. option 2) If option 1 is not possible, remove the incomplete PMD from dpdk.org and maintain the existing PMD as the external one by each vendor. This won't change much in the existing situation as this PMD is not standalone and anyway depended on an external code base. I am glad/help to execute option 1 or 2 or help to a new maintainer if he/she would like to step up and take ownership. --- MAINTAINERS | 1 - doc/guides/cryptodevs/armv8.rst | 3 +-- 2 files changed, 1 insertion(+), 3 deletions(-) diff --git a/MAINTAINERS b/MAINTAINERS index b02066270..8096d93c4 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -918,7 +918,6 @@ F: doc/guides/cryptodevs/ccp.rst F: doc/guides/cryptodevs/features/ccp.ini ARMv8 Crypto -M: Jerin Jacob F: drivers/crypto/armv8/ F: doc/guides/cryptodevs/armv8.rst F: doc/guides/cryptodevs/features/armv8.ini diff --git a/doc/guides/cryptodevs/armv8.rst b/doc/guides/cryptodevs/armv8.rst index 1ab40096e..ada2a774d 100644 --- a/doc/guides/cryptodevs/armv8.rst +++ b/doc/guides/cryptodevs/armv8.rst @@ -28,8 +28,7 @@ Installation In order to enable this virtual crypto PMD, user must: -* Download ARMv8 crypto library source code from - `here `_ +* Use ARMv8 crypto library source code from vendor SDK * Export the environmental variable ARMV8_CRYPTO_LIB_PATH with the path where the ``armv8_crypto`` library was downloaded -- 2.23.0