From owner-freebsd-current@FreeBSD.ORG Wed Mar 10 05:48:36 2010 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4DB7F106564A for ; Wed, 10 Mar 2010 05:48:36 +0000 (UTC) (envelope-from ianf@clue.co.za) Received: from inbound01.jnb1.gp-online.net (inbound01.jnb1.gp-online.net [41.161.16.135]) by mx1.freebsd.org (Postfix) with ESMTP id B39E98FC08 for ; Wed, 10 Mar 2010 05:48:33 +0000 (UTC) Received: from [41.154.88.19] (helo=clue.co.za) by inbound01.jnb1.gp-online.net with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from ) id 1NpEmM-0000cK-Jl; Wed, 10 Mar 2010 07:48:22 +0200 Received: from localhost ([127.0.0.1] helo=clue.co.za) by clue.co.za with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1NpEmB-000HID-HK; Wed, 10 Mar 2010 07:48:11 +0200 To: pyunyh@gmail.com From: Ian FREISLICH In-Reply-To: <20100309221240.GR1311@michelle.cdnetworks.com> References: <20100309221240.GR1311@michelle.cdnetworks.com> <20100305210435.GF14818@michelle.cdnetworks.com> <20100305184046.GD14818@michelle.cdnetworks.com> <20100305175639.GB14818@michelle.cdnetworks.com> X-Attribution: BOFH Date: Wed, 10 Mar 2010 07:48:11 +0200 Message-Id: Cc: current@freebsd.org Subject: Re: dev.bce.X.com_no_buffers increasing and packet loss 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: Wed, 10 Mar 2010 05:48:36 -0000 Pyun YongHyeon wrote: > On Tue, Mar 09, 2010 at 11:55:30PM +0200, Ian FREISLICH wrote: > > I set the RX as high as 512 in 64 quanta but it made little difference > > to the interrupt rate. At times where we experience the packet > > loss and com_no_buffers increases, the interrupt rate on between 1 > > and 3 of the 4 bce interfaces fell from about 3200/s to 130/s. > > > > BD chain is just one of parameters. bce(4) controllers also provide > more advanced features that fine control interrupt moderation(TX/RX > ticks). It's hard to explain all the details so you may want to > read public data sheet of bce(4). Thanks. I'll have a read over that. I meant to state that above that whenever the interrupt rate on a controller (or several) falls off, the interrupt CPU usage climbs from about 4% to about 20%. So it seems like something is happening on host that jams up interrupt processing. Ian -- Ian Freislich