DPDK patches and discussions
 help / color / mirror / Atom feed
From: <jerinj@marvell.com>
To: <dev@dpdk.org>
Cc: <akhil.goyal@nxp.com>, <honnappa.nagarahalli@arm.com>,
	<thomas@monjalon.net>, <hemant.agrawal@nxp.com>,
	<anoobj@marvell.com>, <pathreya@marvell.com>,
	<pkapoor@marvell.com>, Jerin Jacob <jerinj@marvell.com>
Subject: [dpdk-dev]  [PATCH] maintainers: update for armv8 crypto library
Date: Sat, 12 Oct 2019 13:04:21 +0530	[thread overview]
Message-ID: <20191012073421.44748-1-jerinj@marvell.com> (raw)

From: Jerin Jacob <jerinj@marvell.com>

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 <jerinj@marvell.com>
---

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 <jerinj@marvell.com>
 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 <https://github.com/caviumnetworks/armv8_crypto>`_
+* 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


             reply	other threads:[~2019-10-12  7:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-12  7:34 jerinj [this message]
2019-10-16 11:35 ` Jerin Jacob
2019-10-22 20:32 ` Honnappa Nagarahalli
2019-10-23  2:50   ` Jerin Jacob
2019-10-23  6:23     ` Thomas Monjalon
2019-10-23  8:12       ` Jerin Jacob
2019-10-23 17:11     ` Honnappa Nagarahalli
2019-10-23 17:28       ` Jerin Jacob
2019-10-23 18:17         ` Honnappa Nagarahalli
2019-10-24 11:36           ` Ferruh Yigit
2019-10-23 17:41       ` Jerin Jacob

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191012073421.44748-1-jerinj@marvell.com \
    --to=jerinj@marvell.com \
    --cc=akhil.goyal@nxp.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=pathreya@marvell.com \
    --cc=pkapoor@marvell.com \
    --cc=thomas@monjalon.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).