DPDK website maintenance
 help / color / mirror / Atom feed
From: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
To: 谈鉴锋 <henry.tjf@antgroup.com>,
	"Thomas Monjalon" <thomas@monjalon.net>,
	"Jill Lovato" <jlovato@linuxfoundation.org>
Cc: tdelanerolle <tdelanerolle@linuxfoundation.org>,
	web <web@dpdk.org>, "谈鉴锋(浩也)" <henry.tjf@antfin.com>,
	"irene.zhang" <irene.zhang@microsoft.com>,
	"maxime.coquelin" <maxime.coquelin@redhat.com>,
	orika <orika@nvidia.com>, guyk <guyk@marvell.com>,
	"周介龙(卓腾)" <jielong.zjl@antfin.com>
Subject: Re: [dpdk-web] update of ecosystem page
Date: Tue, 10 Nov 2020 09:50:24 +0000	[thread overview]
Message-ID: <DM6PR11MB3308CAA6F829D4FFF4A14D629AE90@DM6PR11MB3308.namprd11.prod.outlook.com> (raw)
In-Reply-To: <9d6b0959-f5e9-4ea2-9844-a67dce410a01.henry.tjf@antgroup.com>

Hi Jianfeng,

I am fine either way, one thing that concerns me with TLDKv2 link –
as I can see it is not synced with latest TLDK code (memtank lib is not there).
Do you plan to sync them up somehow?

From: 谈鉴锋 <henry.tjf@antgroup.com>
Sent: Tuesday, November 10, 2020 2:54 AM
To: Thomas Monjalon <thomas@monjalon.net>; Jill Lovato <jlovato@linuxfoundation.org>
Cc: tdelanerolle <tdelanerolle@linuxfoundation.org>; web <web@dpdk.org>; Ananyev, Konstantin <konstantin.ananyev@intel.com>; 谈鉴锋(浩也) <henry.tjf@antfin.com>; irene.zhang <irene.zhang@microsoft.com>; maxime.coquelin <maxime.coquelin@redhat.com>; orika <orika@nvidia.com>; guyk <guyk@marvell.com>; 周介龙(卓腾) <jielong.zjl@antfin.com>
Subject: Re: update of ecosystem page


As a developer and user of TLDK, glad to see this topic.

Recently, we have added more features into TLDK, like SACK, fixed 10+ bugs, 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.

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 edge or telecom boxes.

In all, we'd like to see TLDK shown in this page, and more users can reference it. As for TLDK vs TLDKv2, now we
definitely use TLDKv2. Considering that TLDKv2 provides both l4p and socket interface, I personally think we can move on to TLDKv2.
Konstantin, what's your opinion?


From:Thomas Monjalon <thomas@monjalon.net<mailto:thomas@monjalon.net>>
Send Time:2020年11月9日(星期一) 19:19
To:Jill Lovato <jlovato@linuxfoundation.org<mailto:jlovato@linuxfoundation.org>>
Cc:tdelanerolle <tdelanerolle@linuxfoundation.org<mailto:tdelanerolle@linuxfoundation.org>>; web <web@dpdk.org<mailto:web@dpdk.org>>; AnanyevKonstantin <konstantin.ananyev@intel.com<mailto:konstantin.ananyev@intel.com>>; 谈鉴锋(浩也) <henry.tjf@antfin.com<mailto:henry.tjf@antfin.com>>; irene.zhang <irene.zhang@microsoft.com<mailto:irene.zhang@microsoft.com>>; maxime.coquelin <maxime.coquelin@redhat.com<mailto:maxime.coquelin@redhat.com>>; orika <orika@nvidia.com<mailto:orika@nvidia.com>>; guyk <guyk@marvell.com<mailto:guyk@marvell.com>>
Subject:update of ecosystem page


I'm looking to update the ecosystem page:

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

In the list of device classes, we are missing:
- Regular Expression Engine
- vHost Data Path Acceleration


  reply	other threads:[~2020-11-10  9:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-09 11:18 Thomas Monjalon
2020-11-10  2:54 ` 谈鉴锋
2020-11-10  9:50   ` Ananyev, Konstantin [this message]
2020-12-09 18:33     ` Thomas Monjalon
2020-12-10  3:18       ` 谈鉴锋
2020-12-10  9:20         ` Ananyev, Konstantin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DM6PR11MB3308CAA6F829D4FFF4A14D629AE90@DM6PR11MB3308.namprd11.prod.outlook.com \
    --to=konstantin.ananyev@intel.com \
    --cc=guyk@marvell.com \
    --cc=henry.tjf@antfin.com \
    --cc=henry.tjf@antgroup.com \
    --cc=irene.zhang@microsoft.com \
    --cc=jielong.zjl@antfin.com \
    --cc=jlovato@linuxfoundation.org \
    --cc=maxime.coquelin@redhat.com \
    --cc=orika@nvidia.com \
    --cc=tdelanerolle@linuxfoundation.org \
    --cc=thomas@monjalon.net \
    --cc=web@dpdk.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).