From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264957AbTLKNJO (ORCPT ); Thu, 11 Dec 2003 08:09:14 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264958AbTLKNJN (ORCPT ); Thu, 11 Dec 2003 08:09:13 -0500 Received: from mail-09.iinet.net.au ([203.59.3.41]:27030 "HELO mail.iinet.net.au") by vger.kernel.org with SMTP id S264957AbTLKNJK (ORCPT ); Thu, 11 Dec 2003 08:09:10 -0500 Message-ID: <3FD86C70.5000408@cyberone.com.au> Date: Fri, 12 Dec 2003 00:09:04 +1100 From: Nick Piggin User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030827 Debian/1.4-3 X-Accept-Language: en MIME-Version: 1.0 To: William Lee Irwin III CC: linux-kernel , Ingo Molnar , Rusty Russell , Anton Blanchard , "Martin J. Bligh" , "Nakajima, Jun" , Mark Wong Subject: Re: [CFT][RFC] HT scheduler References: <3FD3FD52.7020001@cyberone.com.au> <20031208155904.GF19412@krispykreme> <3FD50456.3050003@cyberone.com.au> <20031209001412.GG19412@krispykreme> <3FD7F1B9.5080100@cyberone.com.au> <3FD81BA4.8070602@cyberone.com.au> <3FD8317B.4060207@cyberone.com.au> <20031211115222.GC8039@holomorphy.com> In-Reply-To: <20031211115222.GC8039@holomorphy.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org William Lee Irwin III wrote: >On Thu, Dec 11, 2003 at 07:57:31PM +1100, Nick Piggin wrote: > >>OK, it is spinning on .text.lock.futex. The following results are >>top 10 profiles from a 120 rooms run and a 150 rooms run. The 150 >>room run managed only 24.8% the throughput of the 120 room run. >>Might this be a JVM problem? >>I'm using Sun Java HotSpot(TM) Server VM (build 1.4.2_01-b06, mixed mode) >> ROOMS 120 150 >>PROFILES >>total 100.0% 100.0% >>default_idle 81.0% 66.8% >>.text.lock.rwsem 4.6% 1.3% >>schedule 1.9% 1.4% >>.text.lock.futex 1.5% 19.1% >>__wake_up 1.1% 1.3% >>futex_wait 0.7% 2.8% >>futex_wake 0.7% 0.5% >>.text.lock.dev 0.6% 0.2% >>rwsem_down_read_failed 0.5% >>unqueue_me 3.2% >> > >If this thing is heavily threaded, it could be mm->page_table_lock. > I'm not sure how threaded it is, probably very. Would inline spinlocks help show up mm->page_table_lock? It really looks like .text.lock.futex though, doesn't it? Would that be the hashed futex locks? I wonder why it suddenly goes downhill past about 140 rooms though.