From owner-freebsd-current@FreeBSD.ORG Sat Feb 11 00:51:34 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E5AF416A420 for ; Sat, 11 Feb 2006 00:51:34 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9BE3843D46 for ; Sat, 11 Feb 2006 00:51:34 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 5520846B85; Fri, 10 Feb 2006 19:51:22 -0500 (EST) Date: Sat, 11 Feb 2006 00:54:20 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Poul-Henning Kamp In-Reply-To: <5383.1139586916@critter.freebsd.dk> Message-ID: <20060211005336.F90460@fledge.watson.org> References: <5383.1139586916@critter.freebsd.dk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: Andrew Gallatin , current@freebsd.org Subject: Re: [TEST/REVIEW] cpu time accounting patch, step 2 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Feb 2006 00:51:35 -0000 On Fri, 10 Feb 2006, Poul-Henning Kamp wrote: > In message <17388.44976.250463.383429@grasshopper.cs.duke.edu>, Andrew Gallatin > writes: > >> Here are some benchmark results from my "AMD Athlon(tm) 64 X2 Dual Core >> Processor 3800+" running an SMP kernel for both loopback and 10GbE TCP >> networks. The executive summary is that there's a 41% improvement in >> loopback pingpong, and a 12.5% improvement in a pingpong test with a remote >> linux machine over 10GbE. Since the linux machine isn't infinately fast, >> the improvement is probably a bit more than 12.5% ;) > > That's a LOT more than I had hoped for... This is due to our currently rather severe problems with preemption of the sending thread by the netisr on netisr wakeup for loopback transmit. Still cogitating on the right model change for that, but something will go into the tree before 7.0. Robert N M Watson