From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.46.186]) by dpdk.org (Postfix) with ESMTP id E6EB638EB for ; Tue, 9 Sep 2014 08:15:27 +0200 (CEST) Received: by mail.mhcomputing.net (Postfix, from userid 1000) id EE8AE80C764; Mon, 8 Sep 2014 23:20:16 -0700 (PDT) Date: Mon, 8 Sep 2014 23:20:16 -0700 From: Matthew Hall To: zimeiw Message-ID: <20140909062016.GA7050@mhcomputing.net> References: <4a71bb41.1307.14857e341d5.Coremail.zimeiw@163.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4a71bb41.1307.14857e341d5.Coremail.zimeiw@163.com> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: dev@dpdk.org Subject: Re: [dpdk-dev] 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: Tue, 09 Sep 2014 06:15:28 -0000 On Tue, Sep 09, 2014 at 08:49:44AM +0800, zimeiw wrote: > I have porting major FreeBSD tcp/ip stack to dpdk. new tcp/ip stack is based > on dpdk rte_mbuf, rte_ring, rte_memory and rte_table. it is faster to > forwarding packets. Hello, This is awesome work to be doing and badly needed to use DPDK for any L4 purposes where it is very limited. I'll be following your progress. You didn't mention your name, and compare your work with https://github.com/rumpkernel/dpdk-rumptcpip/ , and talk about behavior / performance, and how long you think it'll take. I'm curious if you can give some more comments. I'm implementing an RX-side very basic stack myself... but I'm not using BSD standard APIs or doing TX-side like yours will have. Matthew.