From: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
To: Ingo Molnar <mingo@kernel.org>, Andrea Arcangeli <aarcange@redhat.com>
Cc: Mel Gorman <mgorman@suse.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Rik van Riel <riel@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/2] Simple concepts extracted from tip/numa/core.
Date: Wed, 01 May 2013 23:19:50 +0530 [thread overview]
Message-ID: <20130501174950.7229.15267.sendpatchset@srdronam.in.ibm.com> (raw)
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
next reply other threads:[~2013-05-01 17:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 17:49 Srikar Dronamraju [this message]
2013-05-01 17:50 ` [PATCH 1/2] numa: Track last pid accessing a page Srikar Dronamraju
2013-05-01 17:50 ` [PATCH 2/2] x86, mm: Prevent gcc to re-read the pagetables Srikar Dronamraju
2013-05-03 12:48 ` [PATCH 0/2] Simple concepts extracted from tip/numa/core Mel Gorman
2013-05-08 7:00 ` Srikar Dronamraju
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130501174950.7229.15267.sendpatchset@srdronam.in.ibm.com \
--to=srikar@linux.vnet.ibm.com \
--cc=a.p.zijlstra@chello.nl \
--cc=aarcange@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=riel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome