From: Antti Kantee <pooka@iki.fi>
To: Vincent JARDIN <vincent.jardin@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] announcing rump kernel TCP/IP stack for DPDK
Date: Thu, 23 May 2013 23:41:37 +0200 [thread overview]
Message-ID: <519E8D11.6010106@iki.fi> (raw)
In-Reply-To: <519E7383.6030507@6wind.com>
Vincent,
On 23.05.2013 21:52, Vincent JARDIN wrote:
> We had to develop a complete logic from scratch (aka fast path logic) to
> get a TCP/IP stack with good performances for 6WIND (including some
> Openflow switching). Unfortunately, as part of our DPDK opensource
> contribution, we do not plan to publish under open source our 6WINDGate
> stack (yet).
I'm under no illusion that making things really fast will be trivial
work. If it were, the world would be full of fast TCP/IP stacks ;)
> However, you are very welcomed to introduce a TCP/IP stack for the DPDK.
> What kind of support/benchmark did you run? Would you like to get it
> mainstream into the DPDK?
Our test was simple: DHCP and port 80 "GET /". Since the TCP/IP stack
and rump kernel themselves are solid, it's been my experience that once
the above works, everything works even full blast.
I don't have hardware, but the other party I mentioned in my original
mail wanted to benchmark, so hopefully we'll have some netperf numbers
soon. Based on prior experience, I expect some Gbps throughput on a 10G
without optimizing, but we'll see.
I think currently integration makes sense only as some sort of a
"reachover", i.e. source is not imported into the DPDK tree, but rather
fetched on demand. I'm happy with the current state, but if someone
wants to work on a reachover solution, I'll be happy to assist, though
not drive the effort. Eventually integration may become more pertinent
as different optimizations demand radically different code, but let's
think about that if/when we get there.
br,
antti
next prev parent reply other threads:[~2013-05-23 21:41 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
2013-05-23 19:38 ` Antti Kantee
2013-05-23 19:52 ` Vincent JARDIN
2013-05-23 21:41 ` Antti Kantee [this message]
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=519E8D11.6010106@iki.fi \
--to=pooka@iki.fi \
--cc=dev@dpdk.org \
--cc=vincent.jardin@6wind.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).