From owner-freebsd-current Fri Jun 11 17:22:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1]) by hub.freebsd.org (Postfix) with ESMTP id 10F0B14F34 for ; Fri, 11 Jun 1999 17:22:49 -0700 (PDT) (envelope-from ggm@azure.dstc.edu.au) Received: from azure.dstc.edu.au (azure.dstc.edu.au [130.102.176.27]) by piglet.dstc.edu.au (8.8.7/8.8.7) with ESMTP id KAA25960 for ; Sat, 12 Jun 1999 10:22:48 +1000 (EST) Received: (from ggm@localhost) by azure.dstc.edu.au (8.8.5/8.8.4) id KAA19913 for freebsd-current@FreeBSD.ORG; Sat, 12 Jun 1999 10:22:43 +1000 (EST) Date: Sat, 12 Jun 1999 10:22:43 +1000 (EST) From: George Michaelson Message-Id: <199906120022.KAA19913@azure.dstc.edu.au> To: freebsd-current@FreeBSD.ORG Subject: newbus, sio performance and 'the worst interrupt culprit' Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I too have current (as of last week), newbus, and sio as well as pcm0 I see heaps of lost interrupts. The mail archive has one message saying "newbus broke fast interrupts' but no (not much?) followup to clarify (a) if its still true and (b) what exactly it implies for finding which driver is stealing the interrupt cycle time and causing byteloss on the serial ports. Can somebody provide a canonical answer to why for some people the serial driver performance is off right now? cheers -George To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message