From owner-freebsd-current@FreeBSD.ORG Thu Aug 21 11:37:43 2003 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 5AA4816A4BF for ; Thu, 21 Aug 2003 11:37:43 -0700 (PDT) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CBE143FCB for ; Thu, 21 Aug 2003 11:37:42 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (localhost [127.0.0.1]) by fledge.watson.org (8.12.9/8.12.9) with ESMTP id h7LIbZrO065756; Thu, 21 Aug 2003 14:37:35 -0400 (EDT) (envelope-from robert@fledge.watson.org) Received: from localhost (robert@localhost)h7LIbZkR065753; Thu, 21 Aug 2003 14:37:35 -0400 (EDT) Date: Thu, 21 Aug 2003 14:37:34 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: cosmin In-Reply-To: <20030821181515.GB48349@nacom.phy.uic.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org Subject: Re: malloc message with nfs transfer 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: Thu, 21 Aug 2003 18:37:43 -0000 On Thu, 21 Aug 2003, cosmin wrote: > malloc() of "64" with the following non-sleepable locks held: exclusive > sleep mutex inpr = 0 (0xc4444ef0) locked @ > /usr/src/sys/netinet/udp_usrreq.c:378 exclusive sleep mutex netisr lock > r = 0 (0xc061be80) locked @ /usr/src/sys/net/netisr.c:215 > > I'm getting those on the console, and it seems that they only happen > when users start an nfs transfer to the nfs exported filesystem. The > exported filesystem is a vinum raid5 array but I don't know if that has > anything to do with the messages. Sorry, just to be clear -- is the message you're getting on the NFS client, or the NFS server? Could you turn on debug.witness_ddb and get a stack trace for the warning? > Before I upgraded from 4.8, I used to be able to send at about 8mb/s to > the nfs exported raid5. After upgrading to 5.1-CURRENT, the maximum > speed has been only 4mb/s. I'm wondering if the messages above have > anything to do with the performance drop. You appear to have the kernel debugging features turned to high (which will be useful for resolving this problem :-). Turn off WITNESS and INVARIANTS and you should see a substantial performance improvement. It may not be back up to 4.x levels -- we hope that with ongoing network stack locking work we'll be back to 4.x (and exceed them) in the next few months. Thanks, Robert N M Watson FreeBSD Core Team, TrustedBSD Projects robert@fledge.watson.org Network Associates Laboratories