From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail1.windriver.com (mail1.windriver.com [147.11.146.13]) by dpdk.org (Postfix) with ESMTP id 77CAA1F3 for ; Wed, 18 Sep 2013 01:15:05 +0200 (CEST) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca.corp.ad.wrs.com [147.11.189.40]) by mail1.windriver.com (8.14.5/8.14.3) with ESMTP id r8HNFhD3007505 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Tue, 17 Sep 2013 16:15:43 -0700 (PDT) Received: from ALA-MBA.corp.ad.wrs.com ([169.254.2.42]) by ALA-HCA.corp.ad.wrs.com ([147.11.189.40]) with mapi id 14.02.0347.000; Tue, 17 Sep 2013 16:15:42 -0700 From: "Wiles, Roger Keith" To: "" Thread-Topic: [dpdk-dev] TCP/IP stack - options Thread-Index: AQHOs1+AlQUuCQQZrkuLxwiDAcTeiJnLBkIA Date: Tue, 17 Sep 2013 23:15:42 +0000 Message-ID: <6FE0E642-8D39-4A1A-B690-8788EC840E6A@windriver.com> References: <9C4CB4066E545D4D9D728B3238E19CA501496A96@xmb-aln-x07.cisco.com> In-Reply-To: <9C4CB4066E545D4D9D728B3238E19CA501496A96@xmb-aln-x07.cisco.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [128.224.22.149] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] TCP/IP stack - options 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: Tue, 17 Sep 2013 23:15:05 -0000 Hi Sujith, Wind River also has a fully integrated TCP/IP stack with network accelerati= on using DPKD with INP/AAE product. A few have ported lwIP to DPDK, but the= se 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 wo= rld. We also have a very close relationship with Intel (as we are wholly ow= ned subsidiary of Intel) We have a patent pending socket layer acceleration design and many more fea= tures. Please contact steve.konish@windriver.com or Paul.Senyshyn@windriver.com for mo= re 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] On Sep 17, 2013, at 12:36 AM, Sujith Sankar (ssujith) > 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" > 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. 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