From: Robert Bays <robert@vyatta.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] announcing rump kernel TCP/IP stack for DPDK
Date: Thu, 23 May 2013 13:31:51 -0700 [thread overview]
Message-ID: <CDC3C36D.92E7%rbays@brocade.com> (raw)
In-Reply-To: <519E65A3.1070806@iki.fi>
-----Original Message-----
From: Antti Kantee <pooka@iki.fi>
Date: Thursday, May 23, 2013 11:53 AM
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] announcing rump kernel TCP/IP stack for DPDK
>On 23.05.2013 20:39, Daniel Cegiełka wrote:
>> 2013/5/23 Robert Bays <robert@vyatta.com>:
>>
>>> Of course. And many more times than that. This is one more option
>>>for us and it is BSD licensed.
>>>
>>> Ultimately, we will probably need a TCP stack in there.
>>
>> indeed, but what do you mean by the TCP stack? I hope not the BSD
>>sockets :)
>> rx/tx bufs+simple API is all you need.
>
>Luckily, ripping out sockets and replacing them with a "high-speed
>aware" API is easier than starting from a simple API and implementing
>IPv{4,6}, TCP, IPsec, ...
>
Ugh. We recently switched email to #$@ outlook which goes out if its way
to hide the recipient email address from me. I meant to forward this
email to the Vyatta dev team which is also dev@. Sorry about spamming the
list.
The reason for me forwarding this to my team was that it has been on my
list to research TCP reassembly in DPDK to enable things like application
layer classification.
next prev parent reply other threads:[~2013-05-23 20:31 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 [this message]
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=CDC3C36D.92E7%rbays@brocade.com \
--to=robert@vyatta.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).