Date: Fri, 13 Oct 2000 10:39:14 +0930 From: Greg Lehey <grog@lemis.com> To: Jason Evans <jasone@FreeBSD.org> Cc: FreeBSD SMP list <FreeBSD-smp@FreeBSD.org> Subject: New mutexes (was: cvs commit: src/sys/conf param.c src/sys/kern kern_lock.c src/sys/sys kernel.h lock.h src/sys/vm vm_map.h) Message-ID: <20001013103913.B2467@wantadilla.lemis.com> In-Reply-To: <200010122237.PAA12428@freefall.freebsd.org>; from jasone@FreeBSD.org on Thu, Oct 12, 2000 at 03:37:29PM -0700 References: <200010122237.PAA12428@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, 12 October 2000 at 15:37:29 -0700, Jason Evans wrote: > jasone 2000/10/12 15:37:29 PDT > > Modified files: > sys/conf param.c > sys/kern kern_lock.c > sys/sys kernel.h lock.h > sys/vm vm_map.h > Log: > For lockmgr mutex protection, use an array of mutexes that are allocated > and initialized during boot. This avoids bloating sizeof(struct lock). > As a side effect, it is no longer necessary to enforce the assumtion that > lockinit()/lockdestroy() calls are paired, so the LK_VALID flag has been > removed. I'm just doing the slides for the Con, and going through the sources I note that we have sprouted a plethora of mutexes over the last month. How are we keeping track of them? How does somebody who wants to add a new mutex know where the mines are? Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001013103913.B2467>