DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Antti Kantee <pooka@iki.fi>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] announcing rump kernel TCP/IP stack for DPDK
Date: Thu, 23 May 2013 12:20:24 -0700	[thread overview]
Message-ID: <20130523122024.1dc6837d@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <519E63EA.9020700@iki.fi>

On Thu, 23 May 2013 20:46:02 +0200
Antti Kantee <pooka@iki.fi> wrote:

> On 23.05.2013 19:34, Stephen Hemminger wrote:
> > Already done several times before.
> >   http://savannah.nongnu.org/projects/lwip/
> >   https://code.google.com/p/tcp-ip-in-user-space/
> >   http://www.ohloh.net/p/tcp-ip-in-user-space
> >   http://www.ioremap.net/projects/unetstack
> >   http://www.joerch.org/tcpip/
> >   http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.167.2757
> 
> I'm aware of the paper you linked given that I wrote it.  I don't agree 
> that it supports your claim "already done several times before".

I was more worried about multiple different TCP-IP stacks that seem
to be only used by small number of people and not maintained. Doing full
TCP/IP is hard, and there are lots of features inside.
It would be great to have one that is well supported and maintained.

  reply	other threads:[~2013-05-23 19:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-23 16:40 Antti Kantee
2013-05-23 17:34 ` Stephen Hemminger
2013-05-23 18:22   ` Robert Bays
2013-05-23 18:39     ` Daniel Cegiełka
2013-05-23 18:53       ` Antti Kantee
2013-05-23 20:31         ` Robert Bays
2013-05-23 18:46   ` Antti Kantee
2013-05-23 19:20     ` Stephen Hemminger [this message]
2013-05-23 19:38       ` Antti Kantee
2013-05-23 19:52         ` Vincent JARDIN
2013-05-23 21:41           ` Antti Kantee
2013-05-23 22:05             ` Thomas Monjalon

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=20130523122024.1dc6837d@nehalam.linuxnetplumber.net \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=pooka@iki.fi \
    /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).