From owner-freebsd-current@FreeBSD.ORG  Sat May 10 20:57:21 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 D575B37B401
	for <current@freebsd.org>; Sat, 10 May 2003 20:57:20 -0700 (PDT)
Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B5E8C43F3F
	for <current@freebsd.org>; Sat, 10 May 2003 20:57:19 -0700 (PDT)
	(envelope-from bde@zeta.org.au)
Received: from katana.zip.com.au (katana.zip.com.au [61.8.7.246])
	by mailman.zeta.org.au (8.9.3p2/8.8.7) with ESMTP id NAA13375;
	Sun, 11 May 2003 13:57:07 +1000
Date: Sun, 11 May 2003 13:57:05 +1000 (EST)
From: Bruce Evans <bde@zeta.org.au>
X-X-Sender: bde@gamplex.bde.org
To: David Leimbach <leimy2k@mac.com>
In-Reply-To: <41DA5B37-8330-11D7-9B15-0003937E39E0@mac.com>
Message-ID: <20030511135005.W74110@gamplex.bde.org>
References: <41DA5B37-8330-11D7-9B15-0003937E39E0@mac.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: Lars Eggert <larse@ISI.EDU>
cc: current@freebsd.org
Subject: Re: Interrupt latency problems
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: Sun, 11 May 2003 03:57:21 -0000

On Sat, 10 May 2003, David Leimbach wrote:

> Sorry for being possibly redundant but I think you *must* use sysmouse
> to get rid of
> the latency issues.  I was arguing with the KDE developers for a while

I never use it, and have no latency problems large enough to affect
interactivity :-), though I have diagnostics that detect many problems
just below the interactivity threshold.

MUTEX_PROFILING might be enough to debug Giant lock latency.

Bruce