From owner-freebsd-current Mon Oct 8 22:19: 5 2001 Delivered-To: freebsd-current@freebsd.org Received: from elvis.mu.org (elvis.mu.org [216.33.66.196]) by hub.freebsd.org (Postfix) with ESMTP id 3721637B405 for ; Mon, 8 Oct 2001 22:19:03 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id DEEC781D08; Tue, 9 Oct 2001 00:18:57 -0500 (CDT) Date: Tue, 9 Oct 2001 00:18:57 -0500 From: Alfred Perlstein To: "Kenneth D. Merry" Cc: Terry Lambert , current@FreeBSD.ORG Subject: Re: Why do soft interrupt coelescing? Message-ID: <20011009001857.R59854@elvis.mu.org> References: <3BBF5E49.65AF9D8E@mindspring.com> <20011006144418.A6779@panzer.kdm.org> <3BC00ABC.20ECAAD8@mindspring.com> <20011008231046.A10472@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011008231046.A10472@panzer.kdm.org>; from ken@kdm.org on Mon, Oct 08, 2001 at 11:10:46PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Kenneth D. Merry [011009 00:11] wrote: > > As you say above, this is actually a good thing. I don't see how this ties > into the patch to introduce some sort of interrupt coalescing into the > ti(4) driver. IMO, you should be able to tweak the coalescing parameters > on the board to do what you want. No matter how hard you tweak the board, an interrupt may still trigger while you process a hardware interrupt, this causes an additional poll which can cause additional coalescing. -- -Alfred Perlstein [alfred@freebsd.org] 'Instead of asking why a piece of software is using "1970s technology," start asking why software is ignoring 30 years of accumulated wisdom.' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message