From: Antti Kantee <pooka@iki.fi>
To: dev@dpdk.org
Subject: [dpdk-dev] announcing rump kernel TCP/IP stack for DPDK
Date: Thu, 23 May 2013 18:40:38 +0200 [thread overview]
Message-ID: <519E4686.90406@iki.fi> (raw)
Hi,
I like the opportunities that a technology like DPDK enables, and I felt
that the availability of an open source TCP/IP stack for DPDK could make
things even more interesting. I've been working on a concept called the
anykernel, where the idea is that an OS kernel should be structured in a
fashion which allows the driver components to be run independently of a
monolithic kernel in so-called rump kernels. Long story short, one of
the "byproducts" is a run-anywhere standalone version of NetBSD kernel
TCP/IP stack, so it was a natural progression to integrate that TCP/IP
stack with the NIC driver layer provided by DPDK.
The published code completes "stage 1: make it work". I want to thank
another person who wished to remain anonymous for help with the
implementation and testing. Next up is "stage 2: make it fast". I
welcome everyone to contribute ideas / use cases / code / etc. towards
that goal.
You can find the code for plugging DPDK into the rump kernel NIC layer
along with instructions from:
https://github.com/anttikantee/dpdk-rumptcpip
In case anyone is interested, I tested the setup with Void Linux running
in VM using an emulated 82540 NIC (cf. my previous mail to this list)
and the other party tested on Ubuntu using real hardware and a 82599 NIC.
cheers,
antti
next reply other threads:[~2013-05-23 16:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 16:40 Antti Kantee [this message]
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
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=519E4686.90406@iki.fi \
--to=pooka@iki.fi \
--cc=dev@dpdk.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).