From owner-freebsd-smp Fri Sep 8 0: 5:46 2000 Delivered-To: freebsd-smp@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 18E9D37B422; Fri, 8 Sep 2000 00:05:41 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id SAA25388; Fri, 8 Sep 2000 18:05:22 +1100 Date: Fri, 8 Sep 2000 18:05:18 +1100 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Warner Losh Cc: The Hermit Hacker , freebsd-current@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: 'interrupt-level buffer overflows' for sio device? In-Reply-To: <200009080302.VAA50459@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 7 Sep 2000, Warner Losh wrote: > 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. Not surprising, since sio's bottom half scheduler (schedsofttty()) is now null. The top half apparently only gets scheduled if there is an output interrupt, a fake output interrupt (flags 0x8) a modem status change, or urgent data. Urgent data probably keeps it going for slip and pppd, but there is no urgent data in the termios line discipline. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message