From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267417AbUHSVYk (ORCPT ); Thu, 19 Aug 2004 17:24:40 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267423AbUHSVYk (ORCPT ); Thu, 19 Aug 2004 17:24:40 -0400 Received: from omx2-ext.sgi.com ([192.48.171.19]:35024 "EHLO omx2.sgi.com") by vger.kernel.org with ESMTP id S267417AbUHSVYi (ORCPT ); Thu, 19 Aug 2004 17:24:38 -0400 From: Jesse Barnes To: "Martin J. Bligh" Subject: Re: kernbench on 512p Date: Thu, 19 Aug 2004 17:24:04 -0400 User-Agent: KMail/1.6.2 Cc: hawkes@sgi.com, linux-kernel@vger.kernel.org, wli@holomorphy.com References: <200408191216.33667.jbarnes@engr.sgi.com> <253460000.1092939952@flay> <200408191711.04776.jbarnes@engr.sgi.com> In-Reply-To: <200408191711.04776.jbarnes@engr.sgi.com> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200408191724.04422.jbarnes@engr.sgi.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thursday, August 19, 2004 5:11 pm, Jesse Barnes wrote: > The output is attached (my mailer insists on wrapping it if I inline it). > I used 'lockstat -w'. The highlights: nw spin rjct lock & function 19.0% 81.0% 0% dcache_lock 3.3% 96.7% 0% d_alloc+0x270 2.7% 97.3% 0% d_delete+0x40 18.3% 81.7% 0% d_instantiate+0x90 4.7% 95.3% 0% d_move+0x60 34.6% 65.4% 0% d_rehash+0xe0 19.1% 80.9% 0% dput+0x40 10.5% 89.5% 0% link_path_walk+0xef0 0% 100% 0% sys_getcwd+0x210 41.4% 58.6% 0% rcu_state 61.3% 38.7% 0% __rcu_process_callbacks+0x260 41.4% 58.6% 0% rcu_check_quiescent_state+0xf0 So it looks like the dcache lock is the biggest problem on this system with this load. And although the rcu stuff has improved tremendously for this system, it's still highly contended. Jesse