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 F329711A2 for ; Fri, 13 Mar 2015 07:41:56 +0100 (CET) Received: by mail.mhcomputing.net (Postfix, from userid 1000) id 1BC2980BDAB; Thu, 12 Mar 2015 23:41:03 -0700 (PDT) Date: Thu, 12 Mar 2015 23:41:03 -0700 From: Matthew Hall To: Avi Kivity Message-ID: <20150313064103.GA9389@mhcomputing.net> References: <3ABAA9DB-3F71-44D4-9C46-22933F9F30F0@mhcomputing.net> <20150222160204.20816910@urahara> <20150223211645.GB20766@mhcomputing.net> <54EBA0F2.6040409@cloudius-systems.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <54EBA0F2.6040409@cloudius-systems.com> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: "" Subject: Re: [dpdk-dev] Appropriate DPDK data structures for TCP sockets 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: Fri, 13 Mar 2015 06:41:57 -0000 On Mon, Feb 23, 2015 at 11:51:46PM +0200, Avi Kivity wrote: > https://github.com/cloudius-systems/seastar Hi Avi and others, My code unintentionally ended up looking somewhat like a C version of your seastar C++ code, even though I didn't really look at yours too much when I coded mine as it was using a lot of hardcore C++ features I really don't have any clue about. :) Someday maybe we can all do a bake-off of tests of DPDK TCPs and Host TCPs and see what kind of stability, features, and performance we can get. I didn't use anything too crazy or high performance just yet... just rte_hash and some spinlocks... but I'm keeping all the collective advice in mind to figure out how I'm going to make all this stuff work right soon. Matthew.