Date: Thu, 17 Jul 2008 11:47:06 +0800 From: "Sepherosa Ziehau" <sepherosa@gmail.com> To: "Bruce Evans" <brde@optusnet.com.au> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>, David Christensen <davidch@broadcom.com> Subject: Re: Enabling MSI-X on -CURRENT for New Network Driver Message-ID: <ea7b9c170807162047q27a95e78q36b5b332f16a7622@mail.gmail.com> In-Reply-To: <20080717131000.K2693@besplex.bde.org> References: <5D267A3F22FD854F8F48B3D2B52381932677F1A0C3@IRVEXCHCCR01.corp.ad.broadcom.com> <20080717131000.K2693@besplex.bde.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Jul 17, 2008 at 11:15 AM, Bruce Evans <brde@optusnet.com.au> wrote: > On Wed, 16 Jul 2008, David Christensen wrote: > >> I'm working on adding MSI-X support for a new network driver >> and having some difficulty in actually getting an interrupt. >> Does this look right? > > I don't know, but on FreeBSD cluster machines running RELENG_8 bce > generates too many interrupts -- approx. 46000/second to deliver On dfly, I set the bce_rx_quick_cons_trip to 24 and bce_rx_ticks to 125, else live lock (>40000/sec) is promised when sinking packets @800kpps. I think bce uses the same coal logic as bge, so bce_rx_quick_cons_trip probably could be set to a larger value like 128; didn't have time to test 128 yet. Best Regards, sephe -- Live Free or Die
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ea7b9c170807162047q27a95e78q36b5b332f16a7622>