Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753871Ab3HVPzF (ORCPT ); Thu, 22 Aug 2013 11:55:05 -0400 Received: from g5t0009.atlanta.hp.com ([15.192.0.46]:9480 "EHLO g5t0009.atlanta.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752291Ab3HVPzD (ORCPT ); Thu, 22 Aug 2013 11:55:03 -0400 From: T Makphaibulchoke To: tytso@mit.edu, adilger.kernel@dilger.ca, viro@zeniv.linux.org.uk, linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org Cc: aswin@hp.com, torvalds@linux-foundation.org, T Makphaibulchoke Subject: [PATCH v2 0/2] ext4: increase mbcache scalability Date: Thu, 22 Aug 2013 09:54:34 -0600 Message-Id: <1377186876-57291-1-git-send-email-tmac@hp.com> X-Mailer: git-send-email 1.7.11.3 In-Reply-To: <1374108934-50550-1-git-send-email-tmac@hp.com> References: <1374108934-50550-1-git-send-email-tmac@hp.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3450 Lines: 89 The patch consists of two parts. The first part introduces higher degree of parallelism to the usages of the mb_cache and mb_cache_entries and impacts all ext filesystems. The second part of the patch further increases the scalablity of an ext4 filesystem by having each ext4 fielsystem allocate and use its own private mbcache structure, instead of sharing a single mcache structures across all ext4 filesystems Here are some of the benchmark results with the changes. On a 90 core machine: Here are the performance improvements in some of the aim7 workloads, --------------------------- | | % increase | --------------------------- | alltests | 11.85 | --------------------------- | custom | 14.42 | --------------------------- | fserver | 21.36 | --------------------------- | new_dbase | 5.59 | --------------------------- | new_fserver | 21.45 | --------------------------- | shared | 12.84 | --------------------------- For Swingbench dss workload, with 16 GB database, ------------------------------------------------------------------------------- | Users | 100 | 200 | 300 | 400 | 500 | 600 | 700 | 800 | 900 | ------------------------------------------------------------------------------- | % imprvoment | 8.46 | 8.00 | 7.35 | -.313| 1.09 | 0.69 | 0.30 | 2.18 | 5.23 | ------------------------------------------------------------------------------- | % imprvoment |45.66 |47.62 |34.54 |25.15 |15.29 | 3.38 | -8.7 |-4.98 |-7.86 | | without using| | | | | | | | | | | shared memory| | | | | | | | | | ------------------------------------------------------------------------------- For SPECjbb2013, composite run, -------------------------------------------- | | max-jOPS | critical-jOPS | -------------------------------------------- | % improvement | 5.99 | N/A | -------------------------------------------- On an 80 core machine: The aim7's results for most of the workloads turn out to the same. Here are the results of Swingbench dss workload, ------------------------------------------------------------------------------- | Users | 100 | 200 | 300 | 400 | 500 | 600 | 700 | 800 | 900 | ------------------------------------------------------------------------------- | % imprvoment |-1.79 | 0.37 | 1.36 | 0.08 | 1.66 | 2.09 | 1.16 | 1.48 | 1.92 | ------------------------------------------------------------------------------- The changes have been tested with ext4 xfstests to verify that no regression has been introduced. Changed in v2: - New performance data - New diff summary T Makphaibulchoke (2): mbcache: decoupling the locking of local from global data ext4: each filesystem creates and uses its own mc_cache fs/ext4/ext4.h | 1 + fs/ext4/super.c | 24 ++-- fs/ext4/xattr.c | 51 +++++---- fs/ext4/xattr.h | 6 +- fs/mbcache.c | 293 +++++++++++++++++++++++++++++++++++------------- include/linux/mbcache.h | 10 +- 6 files changed, 269 insertions(+), 116 deletions(-) -- 1.7.11.3 -- 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/