From owner-freebsd-arch@FreeBSD.ORG Mon Jun 2 17:34:41 2008 Return-Path: Delivered-To: arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 020EA1065670 for ; Mon, 2 Jun 2008 17:34:41 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from phk.freebsd.dk (phk.freebsd.dk [130.225.244.222]) by mx1.freebsd.org (Postfix) with ESMTP id CC9618FC25 for ; Mon, 2 Jun 2008 17:34:40 +0000 (UTC) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (unknown [192.168.61.3]) by phk.freebsd.dk (Postfix) with ESMTP id C90EE170E3; Mon, 2 Jun 2008 17:34:38 +0000 (UTC) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.14.2/8.14.2) with ESMTP id m52HYb29006572; Mon, 2 Jun 2008 17:34:37 GMT (envelope-from phk@critter.freebsd.dk) To: Daniel Eischen From: "Poul-Henning Kamp" In-Reply-To: Your message of "Mon, 02 Jun 2008 13:14:10 -0400." Date: Mon, 02 Jun 2008 17:34:37 +0000 Message-ID: <6571.1212428077@critter.freebsd.dk> Sender: phk@critter.freebsd.dk Cc: Ed Schouten , Julian Elischer , arch@freebsd.org Subject: Re: all mutexes -> read-write locks? X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Jun 2008 17:34:41 -0000 In message , Daniel Eischen wri tes: >It doesn't, it shows one reason why mutexes can be different >than read/write locks. Agreed. There is no easy way to determine which mutexes can be rw_locks, so take the correct route: education. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.