From: "Wiles, Roger Keith" <keith.wiles@windriver.com>
To: "<dev@dpdk.org>" <dev@dpdk.org>
Subject: Re: [dpdk-dev] TCP/IP stack - options
Date: Tue, 17 Sep 2013 23:15:42 +0000 [thread overview]
Message-ID: <6FE0E642-8D39-4A1A-B690-8788EC840E6A@windriver.com> (raw)
In-Reply-To: <9C4CB4066E545D4D9D728B3238E19CA501496A96@xmb-aln-x07.cisco.com>
Hi Sujith,
Wind River also has a fully integrated TCP/IP stack with network acceleration using DPKD with INP/AAE product. A few have ported lwIP to DPDK, but these stacks are not fully integrated into the whole system meaning the Linux host (at least I do not know of anyone that does).
Wind River's INP product is a complete TCP/IP stack with many more features and protocols backed by the largest embedded development company in the world. We also have a very close relationship with Intel (as we are wholly owned subsidiary of Intel)
We have a patent pending socket layer acceleration design and many more features.
Please contact steve.konish@windriver.com<mailto:steve.konish@windriver.com> or Paul.Senyshyn@windriver.com<mailto:Paul.Senyshyn@windriver.com> for more details.Keith Wiles, Principal Technologist for Networking member of the CTO office, Wind River
direct 972.434.4136 mobile 940.213.5533 fax 000.000.0000
[Powering 30 Years of Innovation]<http://www.windriver.com/announces/wr30/>
On Sep 17, 2013, at 12:36 AM, Sujith Sankar (ssujith) <ssujith@cisco.com<mailto:ssujith@cisco.com>> wrote:
Hi Vincent,
Sincere thanks to you for the email ! This is very helpful.
I think I'll go with Rump kernel stack to start with, and might think
about the other options later.
Regards,
-Sujith
On 17/09/13 2:01 AM, "Vincent JARDIN" <vincent.jardin@6wind.com<mailto:vincent.jardin@6wind.com>> wrote:
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<http://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 prev parent reply other threads:[~2013-09-17 23:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-16 20:31 [dpdk-dev] " Vincent JARDIN
2013-09-17 4:36 ` [dpdk-dev] " Sujith Sankar (ssujith)
2013-09-17 23:15 ` Wiles, Roger Keith [this message]
2013-09-19 4:37 ` Sujith Sankar (ssujith)
-- strict thread matches above, loose matches on Subject: below --
2013-09-17 13:09 [dpdk-dev] " Gil Hellmann
2013-09-19 4:33 ` [dpdk-dev] " 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=6FE0E642-8D39-4A1A-B690-8788EC840E6A@windriver.com \
--to=keith.wiles@windriver.com \
--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).