From owner-freebsd-arch Mon Sep 11 19:26:19 2000 Delivered-To: freebsd-arch@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id AFA6B37B423 for ; Mon, 11 Sep 2000 19:26:16 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e8C2QAa09517; Mon, 11 Sep 2000 19:26:10 -0700 (PDT) Date: Mon, 11 Sep 2000 19:26:10 -0700 From: Alfred Perlstein To: Jason Evans Cc: Greg Lehey , arch@FreeBSD.ORG Subject: Re: Long-term mutex ownership (was Re: Interruptable mutex aquires.) Message-ID: <20000911192610.D12231@fw.wintelcom.net> References: <200009111815.MAA21525@berserker.bsdi.com> <20000911114746.G12231@fw.wintelcom.net> <20000912114154.H88615@wantadilla.lemis.com> <20000911192425.B31089@blitz.canonware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20000911192425.B31089@blitz.canonware.com>; from jasone@canonware.com on Mon, Sep 11, 2000 at 07:24:25PM -0700 Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Jason Evans [000911 19:24] wrote: > On Tue, Sep 12, 2000 at 11:41:54AM +0930, Greg Lehey wrote: > > I think we need to come to some kind of consensus about how we are > > going to structure locking before we go into this much detail. At the > > moment we don't even agree whether we can hold on to (blocking) > > mutexes for long periods of time. > > I don't recall the original argument against holding mutexes for long > periods. From an abstract point of view, there's nothing wrong with such > practice, and in fact it makes sense for many problems. Is there an issue > with our implementation? If so, can someone please explain it? You are currently unable to abort if a signal comes in. :) Conditional variables add overhead and complexity where it's not needed. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message