From: Thavatchai Makphaibulchoke Subject: Re: [PATCH v4 0/3] ext4: increase mbcache scalability Date: Mon, 27 Jan 2014 05:27:10 -0700 Message-ID: <52E6509E.5080103@hp.com> References: <1377186876-57291-1-git-send-email-tmac@hp.com> <1390588288-66930-1-git-send-email-tmac@hp.com> <87fvodcb65.fsf@tassilo.jf.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: T Makphaibulchoke , "viro@zeniv.linux.org.uk" , "tytso@mit.edu" , "adilger.kernel@dilger.ca" , "linux-ext4@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-fsdevel@vger.kernel.org" , "aswin@hp.com" To: Andreas Dilger , Andi Kleen Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-ext4.vger.kernel.org On 01/24/2014 11:09 PM, Andreas Dilger wrote: > I think the ext4 block groups are locked with the blockgroup_lock that has about the same number of locks as the number of cores, with a max of 128, IIRC. See blockgroup_lock.h. > > While there is some chance of contention, it is also unlikely that all of the cores are locking this area at the same time. > > Cheers, Andreas > Thanks Andreas for the suggestion. Will try that versus adding just a new private spinlock array in mbcache and compare the performance. Thanks, Mak.