[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20130501174950.7229.15267.sendpatchset@srdronam.in.ibm.com>
Date: Wed, 01 May 2013 23:19:50 +0530
From: Srikar Dronamraju <srikar@...ux.vnet.ibm.com>
To: Ingo Molnar <mingo@...nel.org>,
Andrea Arcangeli <aarcange@...hat.com>
Cc: Mel Gorman <mgorman@...e.de>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Rik van Riel <riel@...hat.com>,
LKML <linux-kernel@...r.kernel.org>
Subject: [PATCH 0/2] Simple concepts extracted from tip/numa/core.
Hi,
Here is an attempt to pick few interesting patches from tip/numa/core.
For the initial stuff, I have selected the last_nidpid (which was
last_cpupid + Make gcc to not reread the page tables patches).
Here is the performance results of running autonumabenchmark on a 8 node 64
core system. Each of these tests were run for 5 iterations.
KernelVersion: v3.9
Testcase: Min Max Avg
numa01: 1784.16 1864.15 1800.16
numa01_THREAD_ALLOC: 293.75 315.35 311.03
numa02: 32.07 32.72 32.59
numa02_SMT: 39.27 39.79 39.69
KernelVersion: v3.9 + last_nidpid + gcc: no reread patches
Testcase: Min Max Avg %Change
numa01: 1774.66 1870.75 1851.53 -2.77%
numa01_THREAD_ALLOC: 275.18 279.47 276.04 12.68%
numa02: 32.75 34.64 33.13 -1.63%
numa02_SMT: 32.00 36.65 32.93 20.53%
We do see some degradation in numa01 and numa02 cases. The degradation is
mostly because of the last_nidpid patch. However the last_nidpid helps
thread_alloc and smt cases and forms the basis for few more interesting
ideas in the tip/numa/core.
arch/x86/mm/gup.c | 23 ++++++++++--
include/linux/mm.h | 72 ++++++++++++++++++++++++-------------
include/linux/mm_types.h | 4 +-
include/linux/page-flags-layout.h | 25 ++++++++-----
mm/huge_memory.c | 2 +-
mm/memory.c | 6 ++--
mm/mempolicy.c | 20 ++++++++---
mm/migrate.c | 4 +-
mm/mm_init.c | 10 +++---
mm/mmzone.c | 14 ++++----
mm/page_alloc.c | 4 +-
11 files changed, 120 insertions(+), 64 deletions(-)
--
Thanks and Regards
Srikar
--
Thanks and Regards
Srikar Dronamraju
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists