DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Florin Coras" <fcoras@cisco.com>
Cc: <dev@dpdk.org>, "Ray Kinsella" <mdr@ashroe.eu>
Subject: RE: TCP/IP stack recommendations
Date: Fri, 2 Sep 2022 15:41:30 +0200	[thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35D872E8@smartserver.smartshare.dk> (raw)
In-Reply-To: <87ler6jc9t.fsf@mdr78.vserver.site>

Hi Florin,

Ray Kinsella sent me in your direction...

I'm looking for recommendations (and warnings) regarding open source TCP/IP stacks for DPDK. Seeing that you are deeply involved in the FD.io VPP Host Stack, I hope you are willing to share some thoughts on the topic?


Med venlig hilsen / kind regards

Morten Brørup
CTO


SmartShare Systems A/S
Tonsbakken 16-18
DK-2740 Skovlunde
Denmark

Office      +45 70 20 00 93
Direct      +45 89 93 50 22
Mobile     +45 25 40 82 12

mb@smartsharesystems.com
www.smartsharesystems.com

> -----Original Message-----
> From: Ray Kinsella [mailto:mdr@ashroe.eu]
> Sent: Tuesday, 30 August 2022 11.45
> To: Morten Brørup
> Cc: dev@dpdk.org
> Subject: Re: TCP/IP stack recommendations
> 
> Hi Morten,
> 
> Reach out to Florin Coras over in VPP-land.
> 
> Morten Brørup <mb@smartsharesystems.com> writes:
> 
> > Hi all.
> >
> > Can anyone in here recommend an actively maintained open source
> TCP/IP stack for DPDK?
> >
> >
> > Med venlig hilsen / Kind regards,
> > -Morten Brørup
> 
> 
> --
> Regards, Ray K


  parent reply	other threads:[~2022-09-02 13:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30  8:42 Morten Brørup
2022-08-30  9:44 ` Ray Kinsella
2022-08-30 15:54   ` Honnappa Nagarahalli
2022-09-02 13:41   ` Morten Brørup [this message]
2022-09-03 17:58     ` Ben Magistro

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=98CBD80474FA8B44BF855DF32C47DC35D872E8@smartserver.smartshare.dk \
    --to=mb@smartsharesystems.com \
    --cc=dev@dpdk.org \
    --cc=fcoras@cisco.com \
    --cc=mdr@ashroe.eu \
    /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).