From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rick Jones Subject: Re: spin_lock cause ? Date: Wed, 1 Jun 2016 13:24:31 -0700 Message-ID: <574F447F.1000503@hpe.com> References: <574F15E4.5070008@lexisnexis.com> <4716588.WReR5L1Wkn@milian-kdab2> <20160601181153.GU2563@kernel.org> <574F2F20.2090007@hpe.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from g2t1383g.austin.hpe.com ([15.233.16.89]:45933 "EHLO g2t1383g.austin.hpe.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750765AbcFAUYe (ORCPT ); Wed, 1 Jun 2016 16:24:34 -0400 Received: from g2t2355.austin.hpe.com (g2t2355.austin.hpe.com [15.233.44.28]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by g2t1383g.austin.hpe.com (Postfix) with ESMTPS id C334BCAE for ; Wed, 1 Jun 2016 20:24:33 +0000 (UTC) In-Reply-To: Sender: linux-perf-users-owner@vger.kernel.org List-ID: To: M Kelly , linux-perf-users@vger.kernel.org On 06/01/2016 12:25 PM, M Kelly wrote: > I think I recall you from hp, years ago when I was there :-) > Thanks for the info. I suspect we are too heavy on > pthread_mutex_lock()/unlock() HP-UX has some ways/tools to track mutex contention. Some extensions to give names to mutexes and then get stats on how often one went to grab them and it was held etc etc. Been ages since I used them - I'd hope there was something similar for Linux but I've not played with threads in a very long time. happy benchmarking, rick jones