From owner-freebsd-smp  Thu Sep  7 16: 0:29 2000
Delivered-To: freebsd-smp@freebsd.org
Received: from berserker.bsdi.com (berserker.twistedbit.com [199.79.183.1])
	by hub.freebsd.org (Postfix) with ESMTP
	id A35F237B423; Thu,  7 Sep 2000 16:00:26 -0700 (PDT)
Received: from berserker.bsdi.com (cp@LOCALHOST [127.0.0.1])
	by berserker.bsdi.com (8.9.3/8.9.3) with ESMTP id RAA24702;
	Thu, 7 Sep 2000 17:00:15 -0600 (MDT)
Message-Id: <200009072300.RAA24702@berserker.bsdi.com>
To: Warner Losh <imp@village.org>
Cc: The Hermit Hacker <scrappy@hub.org>, freebsd-current@freebsd.org,
	freebsd-smp@freebsd.org
Subject: Re: 'interrupt-level buffer overflows' for sio device? 
From: Chuck Paterson <cp@bsdi.com>
Date: Thu, 07 Sep 2000 17:00:15 -0600
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

	FYI, this is very likely not caused by the heavy weight
interrupt threads, but rather because the interrupt threads can't
be run because the giant lock is held by a process running in the
kernel. Once we get drivers to have their own locking and pulled out
from under the giant lock this problem should deminish greatly. Before
we can do this there are various infrastructure pieces which must
be made mp safe, such as the lockmanger.

Chuck


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message