DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Philip Prindeville <philipp_subx@redfish-solutions.com>
Cc: dev@dpdk.org
Subject: Re: DPDK packaging and OpenWrt
Date: Tue, 16 May 2023 16:43:08 -0700	[thread overview]
Message-ID: <20230516164308.6a7c00f2@hermes.local> (raw)
In-Reply-To: <0ED3E358-1635-4B3B-8DCB-01CDA08A0F25@redfish-solutions.com>

On Tue, 16 May 2023 17:24:21 -0600
Philip Prindeville <philipp_subx@redfish-solutions.com> wrote:

> >> 11. What is the user-space TCP/IP stack of choice (or reference) for use with DPDK?  
> > 
> > No user-space TCP/IP stack is really robust and that great.
> > VPP has one but it is likely to be specific to using VPP and not sure if you want to go there.
> > I don't think Fedora/Suse/Debian/Ubuntu have packaged any userspace TCP yet.  
> 
> 
> Not robust how?  In terms of performance, security, handling error conditions, having complete feature handlings... ?

TCP with all the features is very complex, heck Linux is still fixing corner cases.
Sure if you want one socket to send an email or print job, then sure. But doing something
at DPDK kind of performance is quite complex.

  parent reply	other threads:[~2023-05-16 23:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-16 19:18 Philip Prindeville
2023-05-16 20:43 ` Stephen Hemminger
2023-05-16 23:24   ` Philip Prindeville
2023-05-16 23:41     ` Stephen Hemminger
2023-05-16 23:43     ` Stephen Hemminger [this message]
2023-05-16 23:06 ` Garrett D'Amore
2023-05-16 23:38   ` Philip Prindeville

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=20230516164308.6a7c00f2@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=philipp_subx@redfish-solutions.com \
    /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).