From owner-freebsd-current@FreeBSD.ORG  Mon Oct 13 21:57:31 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 5A70D16A4B3
	for <current@freebsd.org>; Mon, 13 Oct 2003 21:57:31 -0700 (PDT)
Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 6C00143FBD
	for <current@freebsd.org>; Mon, 13 Oct 2003 21:57:30 -0700 (PDT)
	(envelope-from imp@bsdimp.com)
Received: from localhost (warner@rover2.village.org [10.0.0.1])
	by harmony.village.org (8.12.9p2/8.12.9) with ESMTP id h9E4vLE7051337;
	Mon, 13 Oct 2003 22:57:21 -0600 (MDT)
	(envelope-from imp@bsdimp.com)
Date: Mon, 13 Oct 2003 22:55:19 -0600 (MDT)
Message-Id: <20031013.225519.19308181.imp@bsdimp.com>
To: nate@root.org
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <20031013105145.J28323@root.org>
References: <20031011234314.P23991@root.org>
	<20031012.095503.129593225.imp@bsdimp.com>
	<20031013105145.J28323@root.org>
X-Mailer: Mew version 2.1 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: current@freebsd.org
Subject: Re: Interrupt statistics?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Oct 2003 04:57:31 -0000

In message: <20031013105145.J28323@root.org>
            Nate Lawson <nate@root.org> writes:
: Given that, my biggest concern now is IO corruption.  Are there any
: devices that have a low interrupt rate (or bus mastering rate) that cannot
: handle a few hundred us latency added to their handler startup?  I'm
: thinking something like a floppy drive where the time between interrupts
: is great enough that cpu_idle() is called but that need to be serviced
: quickly or data is over/underrun.

sio/uart

At 115200 baud, you have 173us to service the interrupt when the FIFO
interrupt level is set to HI.  At 460800 at HI you have 43us.  With
the more conservative MED settings, these numbers are 4 times better
(670us and 173us).  200us is smack dab in the middle of these times.
This is inbound data, so things could be idle and there be issues.

Not sure about other devices.

Warner