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 BF2B7A329E for ; Wed, 23 Oct 2019 19:42:13 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id D1E241D161; Wed, 23 Oct 2019 19:42:12 +0200 (CEST) Received: from mail-io1-f65.google.com (mail-io1-f65.google.com [209.85.166.65]) by dpdk.org (Postfix) with ESMTP id 211751D15B for ; Wed, 23 Oct 2019 19:42:12 +0200 (CEST) Received: by mail-io1-f65.google.com with SMTP id q1so26025425ion.1 for ; Wed, 23 Oct 2019 10:42:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=UJHdWv6Sg9VMrjGEw9MDdCxlxCHxbR5tSwWfekqI5So=; b=Qbmjy9hcrpZuOHM8B4picJGKo2SKRg8VPjv1i5t0+qO94NKb4Ec52Y/fhsbVDspEv4 v0hVS2P9slGEthZeWzFo0bbTwqAD5CjfcYtwtWu6m9Pw3ZSGt8zWLtWxKxLDUhlZ+m7o 3hzks76QsRU79gZ/GFrmx7IXL8x5OC9Rc/t0qsMjOg1J6hTeKwC325xYRmzLJK5bHMFx Nsd5kWBSdSbcMlLux4uUGiatnmhbyy+cOjoQG0xjJixC+rVw/sgh2YbXgve4NseZUVVY houNWeLTHk7esBX3WvH3zUcl1norOyAgXXxiWqDy6/mG9CAzXTQ0JAyaAlY1njKpkMI4 Jajg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=UJHdWv6Sg9VMrjGEw9MDdCxlxCHxbR5tSwWfekqI5So=; b=QCCteixTI9TjvY/TF6Od4/vAN7ZxlJ+H6qgl7V9ZsIvknFPdFN0RUYc+f5pbKe6m7Q zdqs8e89BwkmYs0JjklDzx25JfIwlxW+OB3/L4zl91UvrwPyhkG0cZOi/Rqk8+tnV1t6 6hjIEOWStpJ5s4qt3H26p8RsLJBwY8Ag4zeZWUBTSTeKHdnhb8KW8dFZHm4lPxcv7wKK z1RRKwGZATRdrPsG3Z5QPfheE61UoZHSDolTz4byrX+UZO6HlqWX997gpg4rwf5KtfQR PZTmNJrBbac8HAWHRrPxGzjrsJBCiLL8jPngPfhraaQa6c1Jn9hDjEn7anwX9LTDxgdV EEDA== X-Gm-Message-State: APjAAAWGwhnQv+XFx6GZMosW+G3ABGx6LYU97PeQ8KzrQjch7PGVSL7n Py9uw+q7DXQMMBvV4hC4Fh5QYmxewIyZK3d7bQU= X-Google-Smtp-Source: APXvYqxCgBgxzGKp2CzKsSuqSD6cevVS4B/DuSDnUUzfHf7OfXH6aSFarlnCrIxfZ524j7rUGY2AqLB7nC+T/2wH/JY= X-Received: by 2002:a02:cac5:: with SMTP id f5mr10382564jap.113.1571852531143; Wed, 23 Oct 2019 10:42:11 -0700 (PDT) MIME-Version: 1.0 References: <20191012073421.44748-1-jerinj@marvell.com> In-Reply-To: From: Jerin Jacob Date: Wed, 23 Oct 2019 23:11:54 +0530 Message-ID: To: Honnappa Nagarahalli Cc: dpdk-dev , "Akhil.goyal@nxp.com" , "thomas@monjalon.net" , "hemant.agrawal@nxp.com" , "anoobj@marvell.com" , "pathreya@marvell.com" , "pkapoor@marvell.com" , "jerinj@marvell.com" , nd Content-Type: text/plain; charset="UTF-8" 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" On Wed, Oct 23, 2019 at 10:42 PM Honnappa Nagarahalli wrote: > > On Wed, 23 Oct, 2019, 2:02 am Honnappa Nagarahalli, wrote: > > > > > > > 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. > I do not see any issues with this approach. This patch should be changed to reflect this option? > > > > > > In past, there was a concern with this approach about maintaining the assembly code in dpdk.org. Is this concern still valid? > > > > > > > > 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. > IMHO, DPDK defines an interface to integrate an external crypto library. This might be under use by applications. Removing the PMD will break those applications. > > > > DPDK does not define any such interface. It was pushed to external library for the reason mentioned above. > > [Honnappa] So, what should an application which has its own crypto library do when the PMD is removed? Sorry. I missed this question. The reason why it was moved out, is not to have N different crypto library and bind to this, instead of one library where everyone can contribute it. and the interface between library and the PMD is not designed to create a framework. It is crafted in the way, the "current" external library needed and not for the generic case.