From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: [patch 1/2] fs: cleanup files_lock Date: Tue, 16 Mar 2010 07:41:16 -0700 Message-ID: <4B9F988C.6090008@linux.intel.com> References: <20100316094423.GM2869@laptop> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Al Viro , Frank Mayhar , John Stultz , linux-fsdevel@vger.kernel.org, Greg Kroah-Hartman , Alan Cox , "Eric W. Biederman" , Linus Torvalds To: Nick Piggin Return-path: Received: from mga12.intel.com ([143.182.124.36]:38761 "EHLO azsmga102.ch.intel.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S933040Ab0CPOla (ORCPT ); Tue, 16 Mar 2010 10:41:30 -0400 In-Reply-To: <20100316094423.GM2869@laptop> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: , Nick Piggin wrote: > I would like to start sending bits of vfs scalability improvements to > be reviewed and hopefully merged. > > I will start with files_lock. Last time this one came up, it was > criticised because some hoped to get rid of files list, and because > it didn't have enough justification of the scalability improvement. > > For the first criticism, it isn't any more difficult to rip out if > we are ever able to remove files list. For the second, I have gathered > some statistics and written better justification. Andi I believe is > finding kbuild is becoming limited by files lock on larger systems. Yes we're seeing files_list lock as the major bottleneck on a 32 CPU Threads kernel build. I did a quick review of the patch and it looks good to me. Acked-by: Andi Kleen -Andi