From owner-freebsd-net@FreeBSD.ORG Mon Jul 26 20:26:19 2004 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 59A0B16A4CE for ; Mon, 26 Jul 2004 20:26:19 +0000 (GMT) Received: from xorpc.icir.org (xorpc.icir.org [192.150.187.68]) by mx1.FreeBSD.org (Postfix) with ESMTP id 42AE843D58 for ; Mon, 26 Jul 2004 20:26:19 +0000 (GMT) (envelope-from rizzo@icir.org) Received: from xorpc.icir.org (localhost [127.0.0.1]) by xorpc.icir.org (8.12.9p1/8.12.8) with ESMTP id i6QKQJ8M037445; Mon, 26 Jul 2004 13:26:19 -0700 (PDT) (envelope-from rizzo@xorpc.icir.org) Received: (from rizzo@localhost) by xorpc.icir.org (8.12.9p1/8.12.3/Submit) id i6QKQITe037444; Mon, 26 Jul 2004 13:26:18 -0700 (PDT) (envelope-from rizzo) Date: Mon, 26 Jul 2004 13:26:18 -0700 From: Luigi Rizzo To: Kelly Yancey Message-ID: <20040726132618.A37401@xorpc.icir.org> References: <20040726131235.N74984@gateway.posi.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20040726131235.N74984@gateway.posi.net>; from kbyanc@posi.net on Mon, Jul 26, 2004 at 01:18:46PM -0700 cc: freebsd-net@freebsd.org cc: 'James' Subject: Re: device polling takes more CPU hits?? X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Jul 2004 20:26:19 -0000 On Mon, Jul 26, 2004 at 01:18:46PM -0700, Kelly Yancey wrote: ... > Out of curiousity, what sort of testing did you do to arrive at these > settings? I did some testing a while back with a SmartBits box pumping > packets through a FreeBSD 2.8Ghz box configured to route between two em > gigabit interfaces; I found that changing the burst_max and each_burst > parameters had almost no effect on throughput (maximum 1% difference). fast boxes are pci-bus limited, not CPU limited(*) so changing the burst size (which basically amortizes some CPU costs) has little if any effect. (*) this doesn't mean that the box cannot livelock, as depending on the traffic on the bus, the CPU might stall for long intervals waiting for bus transactions to complete, and becomes unable to do anything at all. So you might still need polling. cheers luigi