Date: Thu, 12 Oct 2000 14:17:47 +0900 From: Jun Kuriyama <kuriyama@imgsrc.co.jp> To: current@FreeBSD.ORG Subject: Re: -current grinds exceeding slow Message-ID: <7m3di2ljt0.wl@waterblue.imgsrc.co.jp> In-Reply-To: In your message of "11 Oct 2000 21:07:52 -0700" <20001011210742.B11949@canonware.com> References: <l03130312b60886cc585c@[194.32.164.2]> <XFMail.001011114214.jhb@FreeBSD.org> <7mn1gaenfa.wl@waterblue.imgsrc.co.jp> <20001011210742.B11949@canonware.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 12 Oct 2000 04:08:04 GMT,
Jason Evans <jasone@canonware.com> wrote:
> Do you have the SMP_DEBUG kernel option enabled?
Yes, I had SMP_DEBUG in my kernel configuration.
> 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.
Thank you for your information. I've disabled SMP_DEBUG and it works
with usual speed! I'll keep disabled until your modification will
come.
--
Jun Kuriyama <kuriyama@imgsrc.co.jp> // IMG SRC, Inc.
<kuriyama@FreeBSD.org> // FreeBSD Project
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7m3di2ljt0.wl>