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 6A786C7DA for ; Fri, 26 Jun 2015 09:03:43 +0200 (CEST) Received: by mail.mhcomputing.net (Postfix, from userid 1000) id B29C980A0A6; Fri, 26 Jun 2015 00:01:02 -0700 (PDT) Date: Fri, 26 Jun 2015 00:01:02 -0700 From: Matthew Hall To: Vladimir Medvedkin Message-ID: <20150626070102.GA22448@mhcomputing.net> References: <20150622175302.GA15788@mhcomputing.net> <20150622235102.41c3619a@uryu.home.lan> <20150623063024.GA3458@mhcomputing.net> <20150624041314.GA15524@mhcomputing.net> <20150624042859.GA16171@mhcomputing.net> <20150624051513.GA18427@mhcomputing.net> <20150624175648.GA9719@mhcomputing.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150624175648.GA9719@mhcomputing.net> User-Agent: Mutt/1.5.23 (2014-03-12) Cc: "" Subject: Re: [dpdk-dev] rte_lpm with larger nexthops or another method? 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, 26 Jun 2015 07:03:43 -0000 Hi guys, So I just finally fixed all the weird unit test failures for the basic-mode. But the rte_lpm_lookupx4 will take quite a bit longer because it uses a lot of real weird SSE intrinsic functions I never used before in my life. However pretty soon I should get some kind of results how it will work. Sadly it appears to be only 1/2 as fast as the old version in the benchmarks, but I suspect this wouldn't matter in my specific app, we shall see... Matthew.