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 X-Spam-Level: X-Spam-Status: No, score=-6.1 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,NICE_REPLY_A, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 65450C4320E for ; Wed, 1 Sep 2021 11:14:49 +0000 (UTC) Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by mail.kernel.org (Postfix) with ESMTP id B9A9B61008 for ; Wed, 1 Sep 2021 11:14:48 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org B9A9B61008 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=ashroe.eu Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=dpdk.org Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D1E0940140; Wed, 1 Sep 2021 13:14:47 +0200 (CEST) Received: from mail-108-mta134.mxroute.com (mail-108-mta134.mxroute.com [136.175.108.134]) by mails.dpdk.org (Postfix) with ESMTP id 4FB4C4013F for ; Wed, 1 Sep 2021 13:14:46 +0200 (CEST) Received: from filter004.mxroute.com ([149.28.56.236] filter004.mxroute.com) (Authenticated sender: mN4UYu2MZsgR) by mail-108-mta134.mxroute.com (ZoneMTA) with ESMTPSA id 17ba11176d500074ba.001 for (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES128-GCM-SHA256); Wed, 01 Sep 2021 11:14:41 +0000 X-Zone-Loop: a7e1547b42cda112df3639d3df555f1a430a79af96c3 X-Originating-IP: [149.28.56.236] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ashroe.eu; s=x; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date: Message-ID:From:References:Cc:To:Subject:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=R5dY9Z7KpSrFppabWl+7j4T4OuZV8PG2e618T4YAqds=; b=U2giKQtqfXXGgdatGu4x8GtrF2 42juYd4uglDA78G2/k58C6FVVZzq+WCymm+A716DtuzxZw0uPP9Uf4FcGfmDO3jas0yUUIWLI+S8a mb8UbO0FHMwnFrxUEIl29jukrZdgmHZpCp5BsnPGpVQ6VsJTQ5i1CgtwxsGPe1/8b9txn+RhYFWPm ulKKD1q7S+l/RU6a7j+7zeLuPYU/VGKpao/zO/ePX0W6VMfG2B+6AK8aOW8hTc3uVVH9fkUWYQIRR dFBshtQsjXa3FdJWBgSP6Ne4E+r8zfNN8N17heFtW6t1RopRQ5byDtc9s/T2M9rqWPrGyLyVm5y6g Gb63YwGg==; To: Hemant Agrawal , David Marchand , Nicolas Chautru Cc: dev , Akhil Goyal , Thomas Monjalon , Tom Rix , "mingshan.zhang@intel.com" , "arun.joshi@intel.com" , Maxime Coquelin References: <1630427130-63903-1-git-send-email-nicolas.chautru@intel.com> From: "Kinsella, Ray" Message-ID: Date: Wed, 1 Sep 2021 12:14:38 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-AuthUser: mdr@ashroe.eu Subject: Re: [dpdk-dev] [PATCH v1] bbdev: remove experimental tag from API 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 Sender: "dev" On 01/09/2021 04:52, Hemant Agrawal wrote: >> >> On Tue, Aug 31, 2021 at 6:27 PM Nicolas Chautru >> wrote: >>> >>> This was previously suggested last year >>> >> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatc >>> hes.dpdk.org%2Fproject%2Fdpdk%2Fpatch%2F1593213242-157394-2-git- >> send-e >>> mail- >> nicolas.chautru%40intel.com%2F&data=04%7C01%7Chemant.agrawal% >>> >> 40nxp.com%7Cfcdfb339ec284057db1508d96c9dd048%7C686ea1d3bc2b4c6f >> a92cd99 >>> >> c5c301635%7C0%7C0%7C637660247324212288%7CUnknown%7CTWFpbGZ >> sb3d8eyJWIjo >>> >> iMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1 >> 000& >>> ;sdata=%2FYwaT29I4XlUxedcdCeyvM5z1R5QeNGTLLPY3XQBKjU%3D& >> ;reserved=0 >>> but there was request from community to wait another year to confirm >> formally this api is mature. >> >> The request was to wait for a new vendor (i.e. non Intel) to implement a >> bbdev driver for their hw. >> >> NXP proposed a driver for this class: >> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatch >> work.dpdk.org%2Fproject%2Fdpdk%2Flist%2F%3Fseries%3D16642%26state >> %3D%252A%26archive%3Dboth&data=04%7C01%7Chemant.agrawal% >> 40nxp.com%7Cfcdfb339ec284057db1508d96c9dd048%7C686ea1d3bc2b4c6f >> a92cd99c5c301635%7C0%7C0%7C637660247324212288%7CUnknown%7CT >> WFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLC >> JXVCI6Mn0%3D%7C1000&sdata=iorsQ7wAXyU2%2FaqeV5CrDp9asl8ztZ >> nSrbDuJpCv9Gk%3D&reserved=0 >> >> What is the status of this driver? > > [Hemant] We are in process of resending the patches in next few days. Ok - just so we are clear - the net-net of that, is that the bbdev APIs will be 'experimental' for another year, right? > >> I see no update on the bbdev API, which seems good, but a confirmation is >> needed. >> >> >> -- >> David Marchand >