From owner-freebsd-net@FreeBSD.ORG Wed Jul 4 15:29:30 2012 Return-Path: Delivered-To: net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B1383106566C; Wed, 4 Jul 2012 15:29:30 +0000 (UTC) (envelope-from luigi@onelab2.iet.unipi.it) Received: from onelab2.iet.unipi.it (onelab2.iet.unipi.it [131.114.59.238]) by mx1.freebsd.org (Postfix) with ESMTP id 6EEE38FC14; Wed, 4 Jul 2012 15:29:30 +0000 (UTC) Received: by onelab2.iet.unipi.it (Postfix, from userid 275) id 3A75C7300A; Wed, 4 Jul 2012 17:48:56 +0200 (CEST) Date: Wed, 4 Jul 2012 17:48:56 +0200 From: Luigi Rizzo To: "Alexander V. Chernikov" Message-ID: <20120704154856.GC3680@onelab2.iet.unipi.it> References: <4FF319A2.6070905@FreeBSD.org> <4FF361CA.4000506@FreeBSD.org> <20120703214419.GC92445@onelab2.iet.unipi.it> <4FF36438.2030902@FreeBSD.org> <4FF3E2C4.7050701@FreeBSD.org> <4FF3FB14.8020006@FreeBSD.org> <4FF402D1.4000505@FreeBSD.org> <20120704091241.GA99164@onelab2.iet.unipi.it> <4FF412B9.3000406@FreeBSD.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4FF412B9.3000406@FreeBSD.org> User-Agent: Mutt/1.4.2.3i Cc: Doug Barton , net@freebsd.org Subject: Re: FreeBSD 10G forwarding performance @Intel X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Jul 2012 15:29:30 -0000 On Wed, Jul 04, 2012 at 01:54:01PM +0400, Alexander V. Chernikov wrote: > On 04.07.2012 13:12, Luigi Rizzo wrote: > >Alex, > >i am sure you are aware that in FreeBSD we have netmap too > Yes, I'm aware of that :) > > >which is probably a lot more usable than packetshader > >(hw independent, included in the OS, also works on linux...) > I'm actually not talking about usability and comparison here :). Thay > have nice idea and nice performance graphs. And packetshader is actually > _platform_ with fast packet delivery being one (and the only open) part > of platform. i am not sure if i should read the above as a feature or a limitation :) > > Their graphs shows 40MPPS (27G/64byte) CPU-only IPv4 packet forwarding > on "two four-core Intel Nehalem CPUs (2.66GHz)" which illustrates > software routing possibilities quite clearly. i suggest to be cautious about graphs in papers (including mine) and rely on numbers you can reproduce yourself. As your nice experiments showed (i especially liked when you moved from one /24 to four /28 routes), at these speeds a factor of 2 or more in throughput can easily arise from tiny changes in configurations, bus, memory and CPU speeds, and so on. cheers luigi