From: Vincent JARDIN <vincent.jardin-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: TCP/IP stack - options
Date: Mon, 16 Sep 2013 22:31:05 +0200 [thread overview]
Message-ID: <52376A89.4000504@6wind.com> (raw)
Hi Sujith,
NetBSD/Rump is the only open source TCP/IP stack for DPDK. Some people
may have tried to port LwIP too. As far as we know, only 6WIND has a
robust and fully compliant stack which provides socket APIs to the
applications on top of the DPDK. I'd be pleased to get a list of options
for the DPDK too:
- Rump/NetBSD thanks to Antti
- maybe LwIP TBC
- 6WINDGate's fast path TCP/IP stack
and to list them on dpdk.org.
My 2 cents,
Vincent
> Hi all,
>
> I'm new to DPDK and this group.
>
> In order to try out some of my applications on DPDK, I'd like to know a
> little bit about the options that are there for protocol processing.
> Could someone give info about the TCP/IP stacks that could be used with
> DPDK libraries and applications? Quick googling gave a few names (6Wind,
> rump kernel tcp/ip stack, etc). But some wise words from the group could
> go a long way in helping me out.
>
> Thanks in advance !
> -Sujith
next reply other threads:[~2013-09-16 20:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 20:31 Vincent JARDIN [this message]
[not found] ` <52376A89.4000504-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2013-09-17 4:36 ` TCP/IP stack - options Sujith Sankar (ssujith)
[not found] ` <9C4CB4066E545D4D9D728B3238E19CA501496A96-WE/xwOPrfQK3XNBon3q9EaBKnGwkPULj@public.gmane.org>
2013-09-17 23:15 ` Wiles, Roger Keith
[not found] ` <6FE0E642-8D39-4A1A-B690-8788EC840E6A-CWA4WttNNZF54TAoqtyWWQ@public.gmane.org>
2013-09-19 4:37 ` Sujith Sankar (ssujith)
-- strict thread matches above, loose matches on Subject: below --
2013-09-17 13:09 Gil Hellmann
[not found] ` <A9CF4849-8E10-425D-908D-7652DE6B7DFB-bJEeYj9oJeDQT0dZR+AlfA@public.gmane.org>
2013-09-19 4:33 ` Sujith Sankar (ssujith)
2013-09-05 8:40 Sujith Sankar (ssujith)
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=52376A89.4000504@6wind.com \
--to=vincent.jardin-pdr9zngts4eavxtiumwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@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 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).