From owner-freebsd-current Wed Oct 11 21: 7:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id E861537B502 for ; Wed, 11 Oct 2000 21:07:52 -0700 (PDT) Received: (qmail 77461 invoked by uid 1142); 12 Oct 2000 04:07:52 -0000 Date: 11 Oct 2000 21:07:52 -0700 Date: Wed, 11 Oct 2000 21:07:42 -0700 From: Jason Evans To: Jun Kuriyama Cc: current@FreeBSD.ORG Subject: Re: -current grinds exceeding slow Message-ID: <20001011210742.B11949@canonware.com> References: <7mn1gaenfa.wl@waterblue.imgsrc.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <7mn1gaenfa.wl@waterblue.imgsrc.co.jp>; from kuriyama@imgsrc.co.jp on Thu, Oct 12, 2000 at 12:41:29PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Oct 12, 2000 at 12:41:29PM +0900, Jun Kuriyama wrote: > At 11 Oct 2000 18:43:14 GMT, > John Baldwin wrote: > > I don't know. Can you try to narrow down the date by cvsupping or > > cvs updating with date tags to see when it started slowing down? > > I've checked with -D '2000-10-03 00:00:00 GMT' and -D '2000-10-04 > 12:00:00 GMT'. With previous kernel, "time find /usr/obj" returns 65 > seconds, but with later kernel, it returns 547 seconds (/usr/obj is > NFS mounted from localhost). > > Top command shows many processes locked with MUTEX status. It seems > this is caused by jasone's commit at 3rd Oct... Do you have the SMP_DEBUG kernel option enabled? My changes added lots of mutexes to the kernel, and mtx_validate() iterates through all mutexes for mtx_init() and mtx_destroy() calls if SMP_DEBUG is enabled. I'm working on a change that will use a pool of mutexes that are allocated at boot time, which will make this slow down go away, but it may be a while before it gets checked in. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message