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 0FC26C6CE for ; Tue, 23 Jun 2015 08:33:02 +0200 (CEST) Received: by mail.mhcomputing.net (Postfix, from userid 1000) id 2FF3980A0A6; Mon, 22 Jun 2015 23:30:24 -0700 (PDT) Date: Mon, 22 Jun 2015 23:30:24 -0700 From: Matthew Hall To: Stephen Hemminger Message-ID: <20150623063024.GA3458@mhcomputing.net> References: <5A3882CB-0DE0-43DB-8DCA-051D561AA943@mhcomputing.net> <20150622175302.GA15788@mhcomputing.net> <20150622235102.41c3619a@uryu.home.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150622235102.41c3619a@uryu.home.lan> 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: Tue, 23 Jun 2015 06:33:02 -0000 On Mon, Jun 22, 2015 at 11:51:02PM -0400, Stephen Hemminger wrote: > In order to make Vyatta/Brocade router work with LPM code > I ended up redoing the layout. It is: > > And also several other scalability improvements (plus IPv6) > and the correct handling of /32. > > Unfortunately, this is such a big binary change that I was > reluctant to break any tests or applications using existing code > and therefore never submitted the patches. 1. What you and Vladimir have done to this code kicks total ass and will be a huge help so I am very excited to squeeze in some cycles somewhere to test all of this stuff out ASAP. 2. Vladimir's changes were somewhat smaller, but Stephen yours are larger. Stephen, if you could place them into a cloned copy of DPDK or a branch somewhere for convenient pickup, I think I could help you make a lot of progress. I could help test these fixes in a second app besides your own to get some cross validation, and help make the required cleanups, so we could get a bit more external validation before we try to negotiate a safe way to merge them upstream to Bruce since he is marked as the LPM maintainer. My DPDK fork is located here, for example, but it could really be anywhere you like to put it which I could access. Or even a one-off zip or tarball with the git repo inside and I could host it in my fork or give you access on the fork to push it as a second remote if you are OK to do that... https://github.com/megahall/dpdk_mhall Matthew.