From owner-freebsd-hackers@FreeBSD.ORG Tue Jan 3 20:18:34 2006 Return-Path: X-Original-To: freebsd-hackers@freebsd.org Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E25B516A41F; Tue, 3 Jan 2006 20:18:34 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id EFDF243D83; Tue, 3 Jan 2006 20:18:29 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k03KIQuK075017; Tue, 3 Jan 2006 13:18:26 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <43BADC12.4020204@samsco.org> Date: Tue, 03 Jan 2006 13:18:26 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Eischen References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: freebsd-hackers@freebsd.org, prime Subject: Re: An idea of remove MUTEX_WAKE_ALL X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Jan 2006 20:18:35 -0000 Daniel Eischen wrote: > On Tue, 3 Jan 2006, Scott Long wrote: > > >>>for a bit if the current lock owner is running on another CPU? >>>Do we currently do that? >>> >>>(*) No, I am not referring to spin mutexes. >>> >> >>Adaptive mutexes are enabled by default and have been for at least a >>year. > > > Ahh, then that's what they (Adaptive) do. > Well, it's a bit different from Solaris, I believe. They do not sleep after a certain number of contested spins, and instead just continue to spin. As we reduce the coverage of large contested locks (like Giant) this becomes much less of performance problem, though. Scott