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 8BFE2A04B0; Wed, 9 Dec 2020 19:34:05 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 8302CC926; Wed, 9 Dec 2020 19:34:04 +0100 (CET) Received: from new4-smtp.messagingengine.com (new4-smtp.messagingengine.com [66.111.4.230]) by dpdk.org (Postfix) with ESMTP id 98D09BE79 for ; Wed, 9 Dec 2020 19:34:01 +0100 (CET) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailnew.nyi.internal (Postfix) with ESMTP id 223E15801E1; Wed, 9 Dec 2020 13:33:59 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Wed, 09 Dec 2020 13:33:59 -0500 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=fm2; bh= v8CUDUdVzt7t+/oq4okl3gg+DcZ4P7M6SD7WQTY8gHE=; b=fAQOOjSQYeVpqD9h JfiCYKDzaaxnNJaiChcpyWh3L/0K7cjdCMx5b30jreyfte9J2Pv4oFBgj0ZE6V1N fTN2royiHu2hSo4Epb46N6U8Plnto9Bx8Fe75b6nnnGLCSI640HxVTeK8iKVdmL1 RmDFHd+fT+vpgWVUVd/lzcFk+GWhEjDwCF3e5PXL9xVUwjdecDnsIYUwd2k4bMT8 5E5+D5HNaxzd1dDQhaCMCK2mT3BDF9VzofwPVoeaXIOGwD5aSCmoQLxV2Vr1vhbh 1lfHN7KSybIVRVpRLdxa98DuAf8oyU11VrnP/VE8uAVAqlr1PdcOBQhij+Qp+M5o Qop4Uw== 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=fm1; bh=v8CUDUdVzt7t+/oq4okl3gg+DcZ4P7M6SD7WQTY8g HE=; b=gWmP/z04V+AdPw0cxMv1WkzpHta/DRux46fUgb2OcgLvnnwJnjWbKqPj/ jPxJK3QSjZjZ4JgZZLp/79ApzbdFkKSYtZzU1nQtrdZyUn78lDMQF1EDezr1ynLN 74YxHv1kbwJUo8Y+KwDgNkDzLIVHzibqB+vxqmub8LJJZfjA8pvPxBavAJYsIhut T1N0ZOOVLETd8PW7kD2U8IEdsUTFRwefAoql+vl39F5nvO1xCeML4ZKtMnpX3+6+ BXYDOSjeidTUASrg4jRd/MG/UEOrUnOVraAXfrOCiVPktH1z4AtzALsbGrDi+Eum YWXSmBtY2cgEH1XW4HW/AzM1WoK0Q== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedujedrudejkedgudduhecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpefhvffufffkjghfggfgtgesthhqredttddtjeenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpeeuudekgeeljeejhefgvdegieejvdeiveekudduteethfduueeg jeejudduvdektdenucffohhmrghinhepughpughkrdhorhhgpdgrnhhshihunhdrtghomh dpfhdqshhtrggtkhdrohhrghdpghhithhhuhgsrdgtohhmnecukfhppeejjedrudefgedr vddtfedrudekgeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpehthhhomhgrshesmhhonhhjrghlohhnrdhnvght 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 C928F108005C; Wed, 9 Dec 2020 13:33:55 -0500 (EST) From: Thomas Monjalon To: =?utf-8?B?6LCI6Ym06ZSL?= , "Ananyev, Konstantin" Cc: Jill Lovato , tdelanerolle , web , =?utf-8?B?6LCI6Ym06ZSLKOa1qeS5nyk=?= , "irene. zhang" , "maxime. coquelin" , orika , guyk , =?utf-8?B?5ZGo5LuL6b6ZKOWNk+iFvik=?= Date: Wed, 09 Dec 2020 19:33:54 +0100 Message-ID: <2816491.2v5P6D5Xc7@thomas> In-Reply-To: References: <5003973.Qp3lsEsask@thomas> <9d6b0959-f5e9-4ea2-9844-a67dce410a01.henry.tjf@antgroup.com> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-web] update of ecosystem page X-BeenThere: web@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK website maintenance List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: web-bounces@dpdk.org Sender: "web" Any conclusion about TLDKv2? I think we'll go with the general link to TLDK. Anyway, TLDKv2 should be merged in the main branch when ready, right? 10/11/2020 10:50, Ananyev, Konstantin: > Hi Jianfeng, >=20 > I am fine either way, one thing that concerns me with TLDKv2 link =E2=80= =93 > as I can see it is not synced with latest TLDK code (memtank lib is not t= here). > Do you plan to sync them up somehow? > Konstantin >=20 >=20 > From: =E8=B0=88=E9=89=B4=E9=94=8B > Sent: Tuesday, November 10, 2020 2:54 AM > To: Thomas Monjalon ; Jill Lovato > Cc: tdelanerolle ; web ; = Ananyev, Konstantin ; =E8=B0=88=E9=89=B4=E9= =94=8B(=E6=B5=A9=E4=B9=9F) ; irene.zhang ; maxime.coquelin ; orika ; guyk ; =E5=91=A8=E4=BB=8B=E9=BE=99(=E5=8D= =93=E8=85=BE) > Subject: Re: update of ecosystem page >=20 > +Jielong >=20 > As a developer and user of TLDK, glad to see this topic. >=20 > Recently, we have added more features into TLDK, like SACK, fixed 10+ bug= s, and deployed TLDK into online applications. > From our side, we would continue to use and invest TLDK, and open source = what we have in TLDK. >=20 > As you can see in our case, TLDK and DPDK can be used in cloud-native env= , besides network-type application, like LB, DNS, etc. > It's a much larger deployment than the later sitting at the data center e= dge or telecom boxes. >=20 > In all, we'd like to see TLDK shown in this page, and more users can refe= rence it. As for TLDK vs TLDKv2, now we > definitely use TLDKv2. Considering that TLDKv2 provides both l4p and sock= et interface, I personally think we can move on to TLDKv2. > Konstantin, what's your opinion? >=20 > Thanks, > Jianfeng >=20 >=20 >=20 >=20 >=20 >=20 > ------------------------------------------------------------------ > From:Thomas Monjalon > > Send Time:2020=E5=B9=B411=E6=9C=889=E6=97=A5(=E6=98=9F=E6=9C=9F=E4=B8=80)= 19:19 > To:Jill Lovato > > Cc:tdelanerolle >; web >; AnanyevKonstan= tin >; = =E8=B0=88=E9=89=B4=E9=94=8B(=E6=B5=A9=E4=B9=9F) >; irene.zhang >; maxime.coquelin >; orika >; guyk > > Subject:update of ecosystem page >=20 > Hi, >=20 > I'm looking to update the ecosystem page: > https://www.dpdk.org/ecosystem/ >=20 > In the list of projects using DPDK, > - ANS got a website: http://www.ansyun.com/ > - F-Stack is missing: http://www.f-stack.org/ > - TLDK is missing: https://github.com/FDio/tldk/ > Should we prefer TLDKv2? https://github.com/FDio/tldk/tree/dev-next-socket > - demikernel/catnip is missing: https://github.com/demikernel/demikernel/= tree/master/src/rust/catnip >=20 > In the list of device classes, we are missing: > - Regular Expression Engine > - vHost Data Path Acceleration >=20 > Thanks >=20 >=20