From: Antti Kantee <pooka-X3B1VOXEql0@public.gmane.org>
To: Stephen Hemminger
<stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: announcing rump kernel TCP/IP stack for DPDK
Date: Thu, 23 May 2013 21:38:44 +0200 [thread overview]
Message-ID: <519E7044.8070403@iki.fi> (raw)
In-Reply-To: <20130523122024.1dc6837d-We1ePj4FEcvRI77zikRAJc56i+j3xesD0e7PPNI6Mm0@public.gmane.org>
On 23.05.2013 21:20, Stephen Hemminger wrote:
>> 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.
I'm also well aware that doing TCP/IP right is very very hard. It's not
possible sit down with the spec for a weekend, write up some code, and
hope it will work in the real world. That's why I didn't implement
TCP/IP. The implementation I mentioned is the unmodified NetBSD kernel
TCP/IP stack running on a very thin hypervisor layer. It's not
maintained by a few people, it's literally maintained by the entire
NetBSD community. Furthermore, it's not a set of patches available for
the NetBSD kernel updated every now and then, it's literally [in] the
kernel. It's been working this way since 2008. What I did now was just
write 200 lines of code to plug the TCP/IP stack onto DPDK.
Hopefully that convinced you that it's not just some random one-shot
kinda-works-except-in-reality bitrot attractor ;)
- antti
next prev parent reply other threads:[~2013-05-23 19:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 16:40 announcing rump kernel TCP/IP stack for DPDK Antti Kantee
[not found] ` <519E4686.90406-X3B1VOXEql0@public.gmane.org>
2013-05-23 17:34 ` Stephen Hemminger
[not found] ` <20130523103445.2dc6feb5-We1ePj4FEcvRI77zikRAJc56i+j3xesD0e7PPNI6Mm0@public.gmane.org>
2013-05-23 18:22 ` Robert Bays
[not found] ` <893EE22D-E168-480C-90C3-E264E0163994-ZtmgI6mnKB3QT0dZR+AlfA@public.gmane.org>
2013-05-23 18:39 ` Daniel Cegiełka
[not found] ` <CAPLrYETyYXJ02KKSpMFRav43ZhET-JxpDWNfPGWpFVw+8yzecw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-05-23 18:53 ` Antti Kantee
[not found] ` <519E65A3.1070806-X3B1VOXEql0@public.gmane.org>
2013-05-23 20:31 ` Robert Bays
2013-05-23 18:46 ` Antti Kantee
[not found] ` <519E63EA.9020700-X3B1VOXEql0@public.gmane.org>
2013-05-23 19:20 ` Stephen Hemminger
[not found] ` <20130523122024.1dc6837d-We1ePj4FEcvRI77zikRAJc56i+j3xesD0e7PPNI6Mm0@public.gmane.org>
2013-05-23 19:38 ` Antti Kantee [this message]
[not found] ` <519E7044.8070403-X3B1VOXEql0@public.gmane.org>
2013-05-23 19:52 ` Vincent JARDIN
[not found] ` <519E7383.6030507-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-05-23 21:41 ` Antti Kantee
[not found] ` <519E8D11.6010106-X3B1VOXEql0@public.gmane.org>
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=519E7044.8070403@iki.fi \
--to=pooka-x3b1voxeql0@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.