From: Mel Gorman <mgorman@suse.de>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux-MM <linux-mm@kvack.org>, Rik van Riel <riel@redhat.com>,
Kevin Hilman <khilman@linaro.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Paul Bolle <paul.bollee@gmail.com>,
Zlatko Calusic <zcalusic@bitsync.net>,
Andrew Morton <akpm@linux-foundation.org>,
Tim Chen <tim.c.chen@linux.intel.com>,
Andi Kleen <ak@linux.intel.com>, Vlastimil Babka <vbabka@suse.cz>
Subject: Re: NUMA? bisected performance regression 3.11->3.12
Date: Tue, 26 Nov 2013 10:32:23 +0000 [thread overview]
Message-ID: <20131126103223.GG5285@suse.de> (raw)
In-Reply-To: <528E8FCE.1000707@intel.com>
On Thu, Nov 21, 2013 at 02:57:18PM -0800, Dave Hansen wrote:
> Hey Johannes,
>
> I'm running an open/close microbenchmark from the will-it-scale set:
> > https://github.com/antonblanchard/will-it-scale/blob/master/tests/open1.c
>
> I was seeing some weird symptoms on 3.12 vs 3.11. The throughput in
> that test was going from down from 50 million to 35 million.
>
> The profiles show an increase in cpu time in _raw_spin_lock_irq. The
> profiles pointed to slub code that hasn't been touched in quite a while.
> I bisected it down to:
>
Dave, do you mind retesting this against "[RFC PATCH 0/5] Memory compaction
efficiency improvements" please? I have not finished reviewing the series
yet but patch 3 mentions lower allocation success rates with Johannes'
patch and notes that it is unlikely to be a bug with the patch itself.
--
Mel Gorman
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-11-26 10:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-21 22:57 NUMA? bisected performance regression 3.11->3.12 Dave Hansen
2013-11-22 5:22 ` Johannes Weiner
2013-11-22 6:18 ` Dave Hansen
2013-11-22 6:38 ` Johannes Weiner
2013-11-22 16:57 ` Dave Hansen
2013-11-26 10:32 ` Mel Gorman [this message]
2013-12-06 17:43 ` Dave Hansen
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=20131126103223.GG5285@suse.de \
--to=mgorman@suse.de \
--cc=aarcange@redhat.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=hannes@cmpxchg.org \
--cc=khilman@linaro.org \
--cc=linux-mm@kvack.org \
--cc=paul.bollee@gmail.com \
--cc=riel@redhat.com \
--cc=tim.c.chen@linux.intel.com \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
--cc=zcalusic@bitsync.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.