From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id C9995A00C5; Tue, 19 Jul 2022 14:12:40 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 743F640A8B; Tue, 19 Jul 2022 14:12:40 +0200 (CEST) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by mails.dpdk.org (Postfix) with ESMTP id 68BC640A8A for ; Tue, 19 Jul 2022 14:12:39 +0200 (CEST) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id D38D95C00CA; Tue, 19 Jul 2022 08:12:38 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Tue, 19 Jul 2022 08:12:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to; s=fm3; t=1658232758; x= 1658319158; bh=f882A541MP6tq/QfyIWnXqyWgjufbREov4Bj4l45rjU=; b=a bBzmB2pt5vuwvK61/mRjISumSTZ3Kbz8XbJ0yrTZiOBglpllOv9q7utjicL6blnK WlMCQYXLkaRFDSqpDdOHXekgRHoNvUrhVs4eSaDOjGFJi5ZLT6d5bM+plTIR3QFR 79/gnQGQ9khyTqT3ZzhexUcO8+IZVdj31nSOIakvuFSuvsN+t0RVzQs+1iLg8Hva sEeiWi0AecBBgznrH/UnODaP68tOUQQIjKvIZjwAud7qI9IZJtvhsjffhvP4HKCd m0eOyxFNdagETdfUa+WEH4t0j2t9eJxEzq/FawHvnBAX1rfE/XnxzCUmG9oJF0zj My54/5NaxpGwck5G43wSg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:date:feedback-id:feedback-id:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to:x-me-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; t=1658232758; x=1658319158; bh=f 882A541MP6tq/QfyIWnXqyWgjufbREov4Bj4l45rjU=; b=WFo1oD0th1MBNCnv8 2mZhkO4rHh3ioQ5HYNX2M6yJceHbLo32oSTWK9/6JB0cEDRAoMkVEbKKiexQQsEw jME1YMuQq5c2pGtTLYZjkK+t4oUe+EnFeqPaH7xgv/rpLFcS/u/9E8x4k4r0RNAr QlW19hjf7k7GJzpaPFHeZFldWhbO7OoUKR/3rIsjz52+K1d0Yg+Nwa12UMVBEVwK 39WaTWAYwPULmrOT5ZErtDhDFxg6eFqx/spq8/oiDbcqToG+zkTNzvmtGsEoDcnZ CRbBkBiKpqGDz5e9VEZKKqwvKXYwSNit4HcZCXhVoMb3bpUraierrY8KLejDnu96 dLCAw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrudeltddggeelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecugg ftrfgrthhtvghrnhepheeuvdfghfevhfettdekhefhueffueffheeuhedtgeelleeugeeu geduueehgfeinecuffhomhgrihhnpeigihhlihhngidrtghomhdpughpughkrdhorhhgne cuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhm rghssehmohhnjhgrlhhonhdrnhgvth X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 19 Jul 2022 08:12:37 -0400 (EDT) From: Thomas Monjalon To: hemant.agrawal@nxp.com, Hemant Agrawal , dev@dpdk.org, maxime.coquelin@redhat.com, david.marchand@redhat.com, hemant.agrawal@nxp.com, Gagandeep Singh , aman.kumar@vvdntech.in Subject: Re: [RFC PATCH 00/29] cover letter for net/qdma PMD Date: Tue, 19 Jul 2022 14:12:35 +0200 Message-ID: <6797649.18pcnM708K@thomas> In-Reply-To: References: <20220706075219.517046-1-aman.kumar@vvdntech.in> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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 18/07/2022 20:15, aman.kumar@vvdntech.in: > On 07/07/22 7:49 pm, Hemant Agrawal wrote: > > > > On 7/7/2022 7:45 PM, Thomas Monjalon wrote: > > > 07/07/2022 15:55, Aman Kumar: > > >> On 07/07/22 12:27 pm, Thomas Monjalon wrote: > > >>> 06/07/2022 09:51, Aman Kumar: > > >>>> This patch series provides net PMD for VVDN's NR(5G) Hi-PHY > > >>>> solution over > > >>>> T1 telco card. These telco accelerator NIC cards are targeted for > > >>>> ORAN DU > > >>>> systems to offload inline NR Hi-PHY (split 7.2) operations. For the > > >>>> DU host, > > >>>> the cards typically appears as a basic NIC device. The device is > > >>>> based on > > >>>> AMD/Xilinx's Ultrasale MPSoC and RFSoC FPGA for which the inline > > >>>> Hi-PHY IP > > >>>> is developed by VVDN Technologies Private Limited. > > >>>> PCI_VENDOR: 0x1f44, Supported Devices: 0x0201, 0x0281 > > >>>> > > >>>> Hardware-specs: > > >>>> https://www.xilinx.com/publications/product-briefs/xilinx-t1-product-brief.pdf > > >>>> > > >>>> > > >>>> - This series is an RFC and target for DPDK v22.11. > > >>>> - Currently, the PMD is supported only for x86_64 host. > > >>>> - Build machine used: Fedora 36 with gcc 12.1.1 > > >>>> - The device communicates to host over AMD/Xilinx's QDMA subsystem for > > >>>> PCIe interface. Link: https://docs.xilinx.com/r/en-US/pg302-qdma > > >>> That's unfortunate, there is something else called QDMA in NXP > > >>> solution: > > >>> https://git.dpdk.org/dpdk/tree/drivers/dma/dpaa2 > > >> Is this going to create a conflict against this submission? I guess > > >> both are publicly available/known for long time. > > > If it's the marketing name, go for it, > > > but it is unfortunate. > > > > QDMA is a very generic name and many vendors have IP for it. > > > > My suggestions is the qualify the specific driver with vendor name i.e. > > amd_qdma or xilinx_qdma or something similar. > > > > NXP also did the same dpaa2_qdma > > > > > @Thomas, @Hemant, > Thank you for highlights and suggestions regarding conflicting names. > We've discussed this internally and came up with below plan. > > For v22.11 DPDK, we would like to submit patches with below renames: > drivers/net/qdma -> drivers/net/t1 > drivers/net/qdma/qdma_*.c/h -> drivers/net/t1/t1_*.c/h > driver/net/qdma/qdma_access -> driver/net/t1/base Curious why "t1"? What is the meaning?