From owner-freebsd-stable@FreeBSD.ORG Mon Jul 24 19:35:25 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4826016A4E2 for ; Mon, 24 Jul 2006 19:35:25 +0000 (UTC) (envelope-from marcelo@registro.br) Received: from clone.registro.br (clone.registro.br [200.160.2.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id D10CA43D4C for ; Mon, 24 Jul 2006 19:35:24 +0000 (GMT) (envelope-from marcelo@registro.br) Received: by clone.registro.br (Postfix, from userid 1014) id E4D652A55B; Mon, 24 Jul 2006 16:35:23 -0300 (BRT) Date: Mon, 24 Jul 2006 16:35:23 -0300 From: Marcelo Gardini do Amaral To: Scott Long Message-ID: <20060724193523.GB51092@registro.br> References: <20060711190908.GC69272@registro.br> <20060720023856.GA65960@sandvine.com> <20060720112613.GB716@turion.vk2pj.dyndns.org> <44BFA2EE.7060308@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44BFA2EE.7060308@samsco.org> User-Agent: Mutt/1.4.2.1i Cc: Peter Jeremy , freebsd-stable@freebsd.org, Ed Maste Subject: Re: How to setup polling on 'bge' interface X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Jul 2006 19:35:25 -0000 > >The limited testing I've done on a Sun V20z at work suggests that you > >can get better routing throughput in interrupt mode than polling mode. > >YMMV and this is before tweaking the polling parameters. (My testing > >also suggests that I don't really need to do any tweaking because > >the limiting factor is the gigabit interfaces rather than the V20z). I've noticed a higher (and variable) RTT with polling mode activated, without tweaking any parameters. > > This might not apply to bge, but the adaptive polling + fast interrupt > changes that I made to if_em earlier in the year were a huge win over > the standard polling code in terms of CPU utilization and packets per > second. I think it also survived a load that caused normal polling to > essentially livelock the machine. And, it had the advantage of > automatically adapting to bursty loads. -- Att., Marcelo Gardini