From owner-freebsd-current Thu Sep 7 20:10: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (CDR27-115.accesscable.net [24.138.27.115]) by hub.freebsd.org (Postfix) with ESMTP id BB3B537B422; Thu, 7 Sep 2000 20:10:03 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.11.0/8.11.0) with ESMTP id e8839AD04714; Fri, 8 Sep 2000 00:09:10 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 8 Sep 2000 00:09:10 -0300 (ADT) From: The Hermit Hacker To: Warner Losh Cc: Bruce Evans , 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-current@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. Okay, I'm a little confused here ... from what I'm reading/following, this isn't a new problem ... or is it? If not, why has it suddenly manifested itself with the new SMP code? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message