From owner-freebsd-current@FreeBSD.ORG Mon Oct 11 18:48:43 2004 Return-Path: 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 A520916A4CE for ; Mon, 11 Oct 2004 18:48:43 +0000 (GMT) Received: from av1-2-sn3.vrr.skanova.net (av1-2-sn3.vrr.skanova.net [81.228.9.106]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6428843D46 for ; Mon, 11 Oct 2004 18:48:43 +0000 (GMT) (envelope-from daniel_k_eriksson@telia.com) Received: by av1-2-sn3.vrr.skanova.net (Postfix, from userid 502) id C031738058; Mon, 11 Oct 2004 20:48:42 +0200 (CEST) Received: from smtp1-2-sn3.vrr.skanova.net (smtp1-2-sn3.vrr.skanova.net [81.228.9.178]) by av1-2-sn3.vrr.skanova.net (Postfix) with ESMTP id AF30737F69 for ; Mon, 11 Oct 2004 20:48:42 +0200 (CEST) Received: from sentinel (h130n1fls11o822.telia.com [213.64.66.130]) by smtp1-2-sn3.vrr.skanova.net (Postfix) with ESMTP id 80F3638009 for ; Mon, 11 Oct 2004 20:48:42 +0200 (CEST) From: "Daniel Eriksson" To: Date: Mon, 11 Oct 2004 20:48:38 +0200 Organization: Home Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.6353 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Thread-Index: AcSvwuu12PSv1nxhQeyoGPlK8KQ/qQ== Subject: Giant-free ahc? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Oct 2004 18:48:43 -0000 Is anyone working on fine-grained locking for the ahc driver? I just upgraded one of my servers from UP to SMP, and noticed that *Giant showed up a lot when running top for processes accessing data on the SCSI discs. It could be a GIANT lock for some other resource of course, but since the ahc driver reports [GIANT-LOCKED] during boot, and since all the processes were accessing data on SCSI discs I just assumed it was waiting for a lock in the ahc driver. Is there a simple way to figure out which resource the processes are waiting for (without compiling in any additional debugging)? /Daniel Eriksson