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 1A4142C7A for ; Thu, 25 Sep 2014 22:03:51 +0200 (CEST) Received: by mail.mhcomputing.net (Postfix, from userid 1000) id 862ED80EF74; Thu, 25 Sep 2014 13:09:39 -0700 (PDT) Date: Thu, 25 Sep 2014 13:09:39 -0700 From: Matthew Hall To: Anjali Kulkarni Message-ID: <20140925200939.GA3565@mhcomputing.net> References: <20140925161124.GA7609@plxv1142.pdx.intel.com> <20140925191820.GA3117@mhcomputing.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] DPDK Demos at IDF conference using DDIO 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, 25 Sep 2014 20:03:51 -0000 On Thu, Sep 25, 2014 at 07:27:21PM +0000, Anjali Kulkarni wrote: > Actually, in the demo that I saw they had probably used as many of the > accelerations as possible to get the kind of rates they described. Even if > we could see (a documentation of) what all things they used in this > particular application, it would help. > From my discussions, it seemed as if there were some specific lookup APIs > that they used to get better performance. > > Anjali Indeed it would be best if this stuff were documented first, then demoed. Otherwise it's hard to get reliably reproducible results. In particular something which went all the way through the processing pipeline from Rx to Tx L1-L7. Matthew.