From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by smtp.lore.kernel.org (Postfix) with ESMTP id 011E1C25B50 for ; Mon, 23 Jan 2023 17:37:10 +0000 (UTC) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 2E46C40150; Mon, 23 Jan 2023 18:37:10 +0100 (CET) Received: from mail-vk1-f178.google.com (mail-vk1-f178.google.com [209.85.221.178]) by mails.dpdk.org (Postfix) with ESMTP id 74824400EF; Mon, 23 Jan 2023 18:37:09 +0100 (CET) Received: by mail-vk1-f178.google.com with SMTP id q21so6334288vka.3; Mon, 23 Jan 2023 09:37:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=BMWVylflVVtvM07meHu6o5psdBGCYSZ4PDlx0s3OSw4=; b=ceVWe59M0V8Y2buHJpHTiVo643vFxQ3yb0K0wWMMglUtTkeE1LUsYcLb6PoKDFf/LY cDhn+gA/9KF8M3jPeEZLjOOu47dpeIdUS4WLgwcW4QISYWWDfmz7nHfsZvx08PrbO79t TZpOngeN1AYPLmiUg5VjySBq9PrbhFOfvW75t2+ko4hC+yWiO9nCFMEw6lo1FYOEH3kh uD46V7Udw8kr2mPdswviQxgeVVCUwmD9GocdUjOu7UFKKIaworvJiTXc08QWttC77Dp5 OpS1xdhvG4iP3fCHv5jXN8zjD8RrWjeZ1o7eZ4O5WCnGYcPXE78sEaknTdc5YmvxTeq5 fMmw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=BMWVylflVVtvM07meHu6o5psdBGCYSZ4PDlx0s3OSw4=; b=OfSRtrtPINjbGpbI2BB3cms40DSeJxVZWt8DZKpMoheR24nvFieqMCTvj4TcxfdQC6 HMUst9WaNosR6o2IUJM5Zky0p+xYXXg67uHjDjkLLKIyIz0yw0hhwAfA9t2Q7ywZf6de Yx4OXU7+6kuwWy6Cmlgptfd+4v/Aftb+WxYG3psFDi1N1znJWs9KyHqvXJMAn6JNKfdJ VfyShGAmsNxUKZWB9jcNbyY4ZGwvpDkRYQOQDtQe5mquXhbuah5PJX4/NboC+C6c3Lvv +nn1TWO/zpCcYDxBTK2OVgS7ccfLIxGnaxyKvgfP7o2qzq2j67vDG+6PxKBVXEKis9xV CDdQ== X-Gm-Message-State: AFqh2kpJAURK5dl6U1q03zwm8jM4KCfatSvvhAGyaOPWCsXkuDCjiV2r O4XTvwQwjLDk51GXFrTwMCHllUkKlOpi1jQuw0s= X-Google-Smtp-Source: AMrXdXszWeTlw08O5S3GlKAT29t8yhiKkBm8Jal1GxL8Nua8zxee4KjtfocScHTV5DQwxtTGHLUCMtpAwtmgV9k6LmI= X-Received: by 2002:a1f:5dc1:0:b0:3e1:9fdf:7740 with SMTP id r184-20020a1f5dc1000000b003e19fdf7740mr3217523vkb.20.1674495428634; Mon, 23 Jan 2023 09:37:08 -0800 (PST) MIME-Version: 1.0 References: <20221027052140.155-1-anoobj@marvell.com> <20221222092522.1628-1-anoobj@marvell.com> <5622577.tWeucmBOSa@thomas> In-Reply-To: <5622577.tWeucmBOSa@thomas> From: Jerin Jacob Date: Mon, 23 Jan 2023 23:06:42 +0530 Message-ID: Subject: Re: [PATCH 0/5] lib: add pdcp protocol To: Thomas Monjalon Cc: Anoob Joseph , Akhil Goyal , Jerin Jacob , Konstantin Ananyev , dev@dpdk.org, Hemant Agrawal , =?UTF-8?Q?Mattias_R=C3=B6nnblom?= , Kiran Kumar K , Volodymyr Fialko , Olivier Matz , techboard@dpdk.org, Nathan Southern , Srikanth Yalavarthi , fengchengwen Content-Type: text/plain; charset="UTF-8" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On Wed, Jan 18, 2023 at 10:09 PM Thomas Monjalon wrote: > > For such new library, I think we need to vote in techboard to accept it. > That's a process we had in recent years to keep the project scope in control. Looks like this process not defined nor documented. In order to bring clarity for new library acceptance and make life easy for contributors (also, less forking the DPDK repo), IMO, we should document the process as there is a lot of effort involved and send multiple version, and finally it gets rejected due to various reasons. I would suggest, some guideline to get started for discussion. I would suggest taking up this for TB meeting to define it. 1)For new library(new directory under lib/ directory) needs to get approval from DPDK tech board. 2)Author needs to send any of the following to start the approval process -Send a write-up on the scope and purpose library. TB may ask for sending API specification RFC is the scope or purpose is not clear. OR -Send RFC with API specification. If it's above, following new libraries needs approval. So I suggest we take approval in coming TB meeting to conclude one way or another. 1) pdcp library (https://patches.dpdk.org/project/dpdk/list/?series=26246) 2) mldev library or device class(https://patches.dpdk.org/project/dpdk/list/?series=25753) 3) memara (https://patches.dpdk.org/project/dpdk/list/?series=26546) 4) pmu ( started as EAL file and moving to separate library at https://patches.dpdk.org/project/dpdk/list/?series=26616) Please add the libraries if I missed something.