From owner-freebsd-current  Thu Sep  7 20: 2:28 2000
Delivered-To: freebsd-current@freebsd.org
Received: from rover.village.org (rover.village.org [204.144.255.49])
	by hub.freebsd.org (Postfix) with ESMTP
	id 9217837B424; Thu,  7 Sep 2000 20:02:24 -0700 (PDT)
Received: from harmony.village.org (harmony.village.org [10.0.0.6])
	by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA40597;
	Thu, 7 Sep 2000 21:02:22 -0600 (MDT)
	(envelope-from imp@harmony.village.org)
Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA50459; Thu, 7 Sep 2000 21:02:11 -0600 (MDT)
Message-Id: <200009080302.VAA50459@harmony.village.org>
To: Bruce Evans <bde@zeta.org.au>
Subject: Re: 'interrupt-level buffer overflows' for sio device? 
Cc: The Hermit Hacker <scrappy@hub.org>, freebsd-current@FreeBSD.ORG,
	freebsd-smp@FreeBSD.ORG
In-reply-to: Your message of "Fri, 08 Sep 2000 11:50:45 +1100."
		<Pine.BSF.4.21.0009081148120.30454-100000@besplex.bde.org> 
References: <Pine.BSF.4.21.0009081148120.30454-100000@besplex.bde.org>  
Date: Thu, 07 Sep 2000 21:02:10 -0600
From: Warner Losh <imp@village.org>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Also, this is interrupt level overflows.  We can run the fast
interrupts fast enough to harvest characters from the hardware.
What's not happening is that sio's bottom half isn't being run fast
enough so the interrupt level buffers overflow.

Warner


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message