Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753833AbZJQXGx (ORCPT ); Sat, 17 Oct 2009 19:06:53 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752539AbZJQXGx (ORCPT ); Sat, 17 Oct 2009 19:06:53 -0400 Received: from cantor.suse.de ([195.135.220.2]:36031 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752356AbZJQXGw (ORCPT ); Sat, 17 Oct 2009 19:06:52 -0400 Date: Sun, 18 Oct 2009 01:06:54 +0200 From: Nick Piggin To: john stultz Cc: paulmck@linux.vnet.ibm.com, Ingo Molnar , Thomas Gleixner , Darren Hart , Clark Williams , Dinakar Guniguntala , lkml Subject: Re: -rt dbench scalabiltiy issue Message-ID: <20091017230654.GC29439@wotan.suse.de> References: <1255723519.5135.121.camel@localhost.localdomain> <20091017004505.GI6720@linux.vnet.ibm.com> <1255741421.5135.145.camel@localhost.localdomain> <1255743456.5135.162.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1255743456.5135.162.camel@localhost.localdomain> User-Agent: Mutt/1.5.9i Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1240 Lines: 24 On Fri, Oct 16, 2009 at 06:37:36PM -0700, john stultz wrote: > Additionally looking at the perf data, it does seem the dcache_lock is > the contention point w/ ext2 on -rt13, but with Nick's patch, the > contention still stays mostly in the dput/path_get functions. So it > seems its just been moved rather then eased with _my port_ of Nick's > patch (emphasis on "my port", since with nick's patch against mainline > there is no regression at all.. I don't want to drag Nick's patches > through the mud here :) No there is nothing to suggest you've done the wrong thing. The dentry refcounting issue was always a known one, and yes looking at the ext3 profiles, ext3/jbd is adding to the refcounting load so it is not surprising that it has slowed down. Also -rt probably has more trouble than mainline when you start hitting spinlock contention. But before turning it back into an atomic, we need to see how far the lock free path walking stuff goes (and that is not finished yet either). -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/