Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752375AbXA1MKo (ORCPT ); Sun, 28 Jan 2007 07:10:44 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752371AbXA1MKo (ORCPT ); Sun, 28 Jan 2007 07:10:44 -0500 Received: from amsfep17-int.chello.nl ([213.46.243.15]:13526 "EHLO amsfep18-int.chello.nl" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1751927AbXA1MKn (ORCPT ); Sun, 28 Jan 2007 07:10:43 -0500 Message-Id: <20070128115118.837777000@programming.kicks-ass.net> User-Agent: quilt/0.45-1 Date: Sun, 28 Jan 2007 12:51:18 +0100 From: Peter Zijlstra To: Andrew Morton , linux-kernel@vger.kernel.org Cc: Ingo Molnar , Peter Zijlstra Subject: [PATCH 0/7] breaking the global file_list_lock Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 726 Lines: 17 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. It has been part of the -rt kernel for some time now and is deemed solid and useful enough to post in its own right. This contention should also occur on the large SMP machines. Feedback would be appreciated, especially with regard to the extra workqueue that was added to flush per cpu lists. Is there an alternative aproach? - 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/