From owner-freebsd-arch Fri May 19 1:42:22 2000 Delivered-To: freebsd-arch@freebsd.org Received: from anchor-post-33.mail.demon.net (anchor-post-33.mail.demon.net [194.217.242.91]) by hub.freebsd.org (Postfix) with ESMTP id 8D91837BEC4; Fri, 19 May 2000 01:42:12 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-33.mail.demon.net with esmtp (Exim 2.12 #1) id 12siME-0005xe-0X; Fri, 19 May 2000 09:42:10 +0100 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA47063; Fri, 19 May 2000 09:47:28 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Fri, 19 May 2000 09:46:24 +0100 (BST) From: Doug Rabson To: Wes Peters Cc: Mike Smith , Chuck Paterson , arch@FreeBSD.ORG Subject: Re: A new api for asynchronous task execution In-Reply-To: <3924E16A.B1123749@softweyr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 19 May 2000, Wes Peters wrote: > Mike Smith wrote: > > > > > > If you are talking about running processes in > > > > order based on scheduling priority, this is propagated > > > > though mutexs which have been blocked on. > > > > > > No, speaking of temporarily elevating the priority of a process holding > > > a lock to the highest priority of all processes blocking on the lock. > > > > You could call this "priority lending" so that the rest of us understand > > what you're talking about. 8) > > The only system I've ever worked on that implements them refer to > them as inversion-safe or inversion-proof semaphores. I've never seen > another name, including "priority lending", in any literature or > article on the subject. Anyway, whatever we choose to call it, the BSD/OS mutex does have support for priority lending. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 20 8442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message