From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.cs.hut.fi (mail.cs.hut.fi [130.233.192.7]) by dpdk.org (Postfix) with ESMTP id 4B5646AA9 for ; Thu, 23 May 2013 20:53:21 +0200 (CEST) Received: from [IPv6:::1] (hutcs.cs.hut.fi [130.233.192.10]) by mail.cs.hut.fi (Postfix) with ESMTPS id 1E1AD308D0A for ; Thu, 23 May 2013 21:53:26 +0300 (EEST) Message-ID: <519E65A3.1070806@iki.fi> Date: Thu, 23 May 2013 20:53:23 +0200 From: Antti Kantee MIME-Version: 1.0 To: dev@dpdk.org References: <519E4686.90406@iki.fi> <20130523103445.2dc6feb5@nehalam.linuxnetplumber.net> <893EE22D-E168-480C-90C3-E264E0163994@vyatta.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-dev] announcing rump kernel TCP/IP stack for DPDK X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 May 2013 18:53:21 -0000 On 23.05.2013 20:39, Daniel Cegiełka wrote: > 2013/5/23 Robert Bays : > >> 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, ...