From owner-freebsd-arch Fri May 19 12:51:10 2000 Delivered-To: freebsd-arch@freebsd.org Received: from berserker.bsdi.com (berserker.twistedbit.com [199.79.183.1]) by hub.freebsd.org (Postfix) with ESMTP id DAA4037BFBE; Fri, 19 May 2000 12:51:06 -0700 (PDT) (envelope-from cp@berserker.bsdi.com) Received: from berserker.bsdi.com (cp@LOCALHOST [127.0.0.1]) by berserker.bsdi.com (8.9.3/8.9.3) with ESMTP id NAA11660; Fri, 19 May 2000 13:51:05 -0600 (MDT) Message-Id: <200005191951.NAA11660@berserker.bsdi.com> To: Mike Smith Cc: arch@freebsd.org Subject: Re: BSD* mutex summary From: Chuck Paterson Date: Fri, 19 May 2000 13:51:05 -0600 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I believe in that in general inheritance and lending are use interchangeably. That's not true either. I think inheritance is in general used to describe both situations. The following quote from a Inside Solaris by Jim Mauro. Chuck Priority inversion describes a scenario where a higher-priority thread is unable to run due to a lower-priority thread holding a resource it needs (for example, a lock). The Solaris kernel addresses the priority inversion problem in its turnstile implementation, providing a priority inheritance mechanism, where the higher-priority thread can will its priority to the lower-priority thread holding the resource it requires. The benefactor of the inheritance, the thread holding the resource, will now have a higher scheduling priority, and thus get scheduled to run sooner so it can finish its work and release the resource, at which point the thread is given its original priority back. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message