DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Yuanhan Liu <yliu@fridaylinux.org>,
	"libtpa@googlegroups.com" <libtpa@googlegroups.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Yuanhan Liu <liuyuanhan.131@bytedance.com>
Subject: RE: [EXT] Libtpa: a DPDK based userspace TCP stack implementation
Date: Mon, 11 Dec 2023 11:32:16 +0000	[thread overview]
Message-ID: <BY3PR18MB478592AF236C7BBDB0285E3CC88FA@BY3PR18MB4785.namprd18.prod.outlook.com> (raw)
In-Reply-To: <ZXbc5oj2Z1DuQvbp@yliu-lap.usts.net>



> -----Original Message-----
> From: Yuanhan Liu <yliu@fridaylinux.org>
> Sent: Monday, December 11, 2023 3:27 PM
> To: libtpa@googlegroups.com
> Cc: dev@dpdk.org; Yuanhan Liu <liuyuanhan.131@bytedance.com>
> Subject: [EXT] Libtpa: a DPDK based userspace TCP stack implementation
> 
> External Email
> 
> ----------------------------------------------------------------------
> Hi all,
> 
> I'd like to share a new DPDK open source project, libtpa(Transport Protocol
> Acceleration)[0], which is just another userspace TCP stack implementation so
> far, written from scratch.
> 
> I started this project 3 years ago, while I was searching for a feasible open
> source project with no luck. There were indeed quite a few options, but none of
> them actually met my needs. I then started writing one. Likely, there are still
> other guys out there looking for a high performance and stable userspace TCP
> stack. This is what this email and libtpa for.

Great Yuanhan.

If you have time and willing to put effort, I suggest make this part of dpdk code base
as new library (tcp or so) and leverage + improve another existing library such ip_frag.

I believe, that is only way.
- This code soon won't soon outdated based on new DPDK version
- More community review and contributors
- More review and features from NIC vendors PoV.
- More arch and driver support.
- More quality

Just my 2c.


  parent reply	other threads:[~2023-12-11 11:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-11  9:56 Yuanhan Liu
2023-12-11 10:57 ` Liang Ma
2023-12-11 11:32 ` Jerin Jacob Kollanukkaran [this message]
2023-12-11 12:16   ` [EXT] " Thomas Monjalon
2023-12-11 12:36     ` Yuanhan Liu
2023-12-11 12:17   ` Yuanhan Liu
2023-12-11 13:40     ` Jerin Jacob

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=BY3PR18MB478592AF236C7BBDB0285E3CC88FA@BY3PR18MB4785.namprd18.prod.outlook.com \
    --to=jerinj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=libtpa@googlegroups.com \
    --cc=liuyuanhan.131@bytedance.com \
    --cc=yliu@fridaylinux.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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).