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 E9C04A0487 for ; Wed, 3 Jul 2019 22:28:01 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id B04CD28EE; Wed, 3 Jul 2019 22:28:01 +0200 (CEST) Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 7E2B4231E for ; Wed, 3 Jul 2019 22:27:59 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 151B721B84; Wed, 3 Jul 2019 16:27:59 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 03 Jul 2019 16:27:59 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=KwxQ2n07fmu5E9O0HkuxjUthP7hfVR/SBzBoxdbhbWU=; b=Zg878badvpZG YzYMXo6/Mo8q+nxggpRiMduzmMeMKQPYjFLo6VIwR8RG6DojoUqLBjRICpeqlXFX gScBMMdo0s+49Jb/rRTHXHWg0Wg5hV60iXF2y6fH4GCRX9v3VnZjL8Xu5//gUBkk gICEJb/fk1zewX27COEcSZk07yC2wgk= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; bh=KwxQ2n07fmu5E9O0HkuxjUthP7hfVR/SBzBoxdbhb WU=; b=LERPuYeGKoSppeJhQVlrTEHYapBDnULdbjLbeQ1jlPJVZH5S7MgjsNSSA fnf5J0X3gRh5Vs63HeccvLAq5CVu++GR0AYWoODJpjsAiQE2UGuq92HygqJsmEfw UILl19ajm7NzlmuYCLoC4N0jOzmJjITl+9nCE8S9UVEDe7jzWrbvmknvjnMQwmOF /otKcWlBckgEeEm7MmS8uBvDW3XcBq5w1zMWQ/bHWBoXoiPM8dB/CuSctSvNTnW2 NECEL6jel49SirFFBqJBQHYS/sTQ1XzgYEOtR4lEYzm+6rep260uCYKXC3jLaoLA S+MufE+Iomi5ztHnLd/cBmF6l7lWQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduvddrfedtgdduheduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvufffkfgjfhgggfgtsehtufertddttddvnecuhfhrohhmpefvhhhomhgr shcuofhonhhjrghlohhnuceothhhohhmrghssehmohhnjhgrlhhonhdrnhgvtheqnecuff homhgrihhnpehinhhtvghlrdgtohhmpdguphgukhdrohhrghenucfkphepjeejrddufeeg rddvtdefrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgrshesmhhonh hjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 78421380083; Wed, 3 Jul 2019 16:27:55 -0400 (EDT) From: Thomas Monjalon To: "Chautru, Nicolas" Cc: "akhil.goyal@nxp.com" , "Yigit, Ferruh" , "Mokhtar, Amr" , "Chalupnik, KamilX" , "Richardson, Bruce" , "dev@dpdk.org" Date: Wed, 03 Jul 2019 22:27:53 +0200 Message-ID: <5502127.KjNqyyhdIp@xps> In-Reply-To: <1183128033837D43A851F70F33ED5C575C1CD663@FMSMSX109.amr.corp.intel.com> References: <1561344776-43990-2-git-send-email-nicolas.chautru@intel.com> <1725731.Q9tSj3VpiJ@xps> <1183128033837D43A851F70F33ED5C575C1CD663@FMSMSX109.amr.corp.intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v6 0/7] bbdev: adding support in BBDEV for 5GNR FEC 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" 03/07/2019 20:31, Chautru, Nicolas: > Thomas wrote: > >> Nicolas Chautru (7): > >> bbdev: renaming non-generic LTE specific structure > >> bbdev: extension of BBDEV API for 5G FEC > >> docs/guides: updating bbdev API for 5GNR operations > >> baseband/turbo_sw: extension of turbosw PMD for 5G > >> docs/guides: updating building steps for BBDEV PMD > >> test-bbdev: update of bbdev test-app for 5GNR > >> test-bbdev: test vectors for 5GNR verification > > > >What are the news about the turbo_sw PMD? > >We are still not able to compile it. > >After a very long time of asking for the dependency, what can be the incentive to get Intel delivering it? > >Should we block any merge in bbdev until it happens? > > Hi Thomas, > What you are referring to was resolved with that previous serie https://patches.dpdk.org/project/dpdk/list/?series=5093&state=* > The turbo_sw_pmd is built by default now and is verified by the DPDK CI. As an option this can be built against the real time signal processing libraries (FlexRAN FEC SDK). The link to latest version of this library is also provided https://software.intel.com/en-us/articles/flexran-lte-and-5g-nr-fec-software-development-kit-modules> Whaouh, it happens and I did not notice it! > I believe that you reviewed this scheme previously earlier Ferruh of the Tech board as you did provide feedback on the related published article as well as recommended to split the previous serie into several patchsets. Indeed, and I did not follow the latest news. > The last serie under review here in that email thread is the extension of the turbo_sw_pmd driver to support 5GNR operations but still rely on the exact same model and dependency, the only limitation is that these libraries requires AVX512 support for 5GNR operations. > > Let me know whether there is any discrepancy and want to discuss further through that mailing list, tech board or other method. In case you are trying to compile the SDK and have any issues let us know as well. That's fine, I can keep cool, thanks.