From owner-freebsd-threads@FreeBSD.ORG Wed Nov 17 19:06:43 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7C10C16A4CE for ; Wed, 17 Nov 2004 19:06:43 +0000 (GMT) Received: from silver.he.iki.fi (helenius.fi [193.64.42.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6193143D2D for ; Wed, 17 Nov 2004 19:06:42 +0000 (GMT) (envelope-from pete@he.iki.fi) Received: from [193.64.42.134] (h86.vuokselantie10.fi [193.64.42.134]) by silver.he.iki.fi (8.13.1/8.11.4) with ESMTP id iAHJ6et5054122 for ; Wed, 17 Nov 2004 21:06:40 +0200 (EET) (envelope-from pete@he.iki.fi) Message-ID: <419BA142.9000801@he.iki.fi> Date: Wed, 17 Nov 2004 21:06:42 +0200 From: Petri Helenius User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040803 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-threads@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: mutex performance X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Nov 2004 19:06:43 -0000 Do you feel that mutex performance could be improved from the current 2-3 million lock/unlock operations per second on uncontested mutexes on ~2.4Ghz prescott? Which seems to be about 1000 cycles per lock/unlock. I have a fairly basic producer/consumer application to optimize and I'm trying to decide on the performance-optimal synchronization method. Pete