From mboxrd@z Thu Jan 1 00:00:00 1970 From: Antti Kantee Subject: Re: announcing rump kernel TCP/IP stack for DPDK Date: Thu, 23 May 2013 20:53:23 +0200 Message-ID: <519E65A3.1070806@iki.fi> References: <519E4686.90406@iki.fi> <20130523103445.2dc6feb5@nehalam.linuxnetplumber.net> <893EE22D-E168-480C-90C3-E264E0163994@vyatta.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable To: dev-VfR2kkLFssw@public.gmane.org Return-path: In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" On 23.05.2013 20:39, Daniel Cegie=C5=82ka wrote: > 2013/5/23 Robert Bays : > >> Of course. And many more times than that. This is one more option fo= r 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 socke= ts :) > rx/tx bufs+simple API is all you need. Luckily, ripping out sockets and replacing them with a "high-speed=20 aware" API is easier than starting from a simple API and implementing=20 IPv{4,6}, TCP, IPsec, ...