Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932715AbXA1On2 (ORCPT ); Sun, 28 Jan 2007 09:43:28 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932737AbXA1On2 (ORCPT ); Sun, 28 Jan 2007 09:43:28 -0500 Received: from pentafluge.infradead.org ([213.146.154.40]:33699 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932715AbXA1On1 (ORCPT ); Sun, 28 Jan 2007 09:43:27 -0500 Date: Sun, 28 Jan 2007 14:43:25 +0000 From: Christoph Hellwig To: Peter Zijlstra Cc: Andrew Morton , linux-kernel@vger.kernel.org, Ingo Molnar Subject: Re: [PATCH 0/7] breaking the global file_list_lock Message-ID: <20070128144325.GB16552@infradead.org> Mail-Followup-To: Christoph Hellwig , Peter Zijlstra , Andrew Morton , linux-kernel@vger.kernel.org, Ingo Molnar References: <20070128115118.837777000@programming.kicks-ass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070128115118.837777000@programming.kicks-ass.net> User-Agent: Mutt/1.4.2.2i X-SRS-Rewrite: SMTP reverse-path rewritten from by pentafluge.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 841 Lines: 19 On Sun, Jan 28, 2007 at 12:51:18PM +0100, Peter Zijlstra wrote: > This patch-set breaks up the global file_list_lock which was found to be a > severe contention point under basically any filesystem intensive workload. Benchmarks, please. Where exactly do you see contention for this? filesystem intensive workload apparently means namespace operation heavy workload, right? The biggest bottleneck I've seen with those is dcache lock. Even if this is becoming a real problem there must be simpler ways to fix this than introducing various new locking primitives and all kinds of complexity. - 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/