linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mel Gorman <mgorman@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Alex Shi <alex.shi@linaro.org>, Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Fengguang Wu <fengguang.wu@intel.com>,
	H Peter Anvin <hpa@zytor.com>, Linux-X86 <x86@kernel.org>,
	Linux-MM <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] Fix ebizzy performance regression due to X86 TLB range flush v2
Date: Sun, 15 Dec 2013 16:17:54 +0000	[thread overview]
Message-ID: <20131215161754.GN11295@suse.de> (raw)
In-Reply-To: <20131215155539.GM11295@suse.de>

On Sun, Dec 15, 2013 at 03:55:39PM +0000, Mel Gorman wrote:
> <SNIP>
> tlbflush micro benchmark
>                     3.13.0-rc3            3.13.0-rc3                3.4.69
>                        vanilla           nowalk-v2r7               vanilla
> Min    1        7.00 (  0.00%)        6.00 ( 14.29%)        5.00 ( 28.57%)
> Min    2        8.00 (  0.00%)        6.00 ( 25.00%)        4.00 ( 50.00%)
> Min    3       13.00 (  0.00%)       11.00 ( 15.38%)        9.00 ( 30.77%)
> Min    4       17.00 (  0.00%)       19.00 (-11.76%)       15.00 ( 11.76%)
> Mean   1       11.28 (  0.00%)       10.66 (  5.48%)        5.17 ( 54.13%)
> Mean   2       11.42 (  0.00%)       11.52 ( -0.85%)        9.04 ( 20.82%)
> Mean   3       23.43 (  0.00%)       21.64 (  7.64%)       10.92 ( 53.39%)
> Mean   4       35.33 (  0.00%)       34.17 (  3.28%)       19.55 ( 44.67%)
> Range  1        6.00 (  0.00%)        7.00 (-16.67%)        4.00 ( 33.33%)
> Range  2       23.00 (  0.00%)       36.00 (-56.52%)       19.00 ( 17.39%)
> Range  3       15.00 (  0.00%)       17.00 (-13.33%)       10.00 ( 33.33%)
> Range  4       29.00 (  0.00%)       26.00 ( 10.34%)        9.00 ( 68.97%)
> Stddev 1        1.01 (  0.00%)        1.12 ( 10.53%)        0.57 (-43.70%)
> Stddev 2        1.83 (  0.00%)        3.03 ( 66.06%)        6.83 (274.00%)
> Stddev 3        2.82 (  0.00%)        3.28 ( 16.44%)        1.21 (-57.14%)
> Stddev 4        6.65 (  0.00%)        6.32 ( -5.00%)        1.58 (-76.24%)
> Max    1       13.00 (  0.00%)       13.00 (  0.00%)        9.00 ( 30.77%)
> Max    2       31.00 (  0.00%)       42.00 (-35.48%)       23.00 ( 25.81%)
> Max    3       28.00 (  0.00%)       28.00 (  0.00%)       19.00 ( 32.14%)
> Max    4       46.00 (  0.00%)       45.00 (  2.17%)       24.00 ( 47.83%)
> 
> <SNIP>
> 
>           3.13.0-rc3  3.13.0-rc3      3.4.69
>              vanilla nowalk-v2r7     vanilla
> User          179.36      165.25       97.29
> System        153.59      155.07      128.32
> Elapsed      1439.52     1437.69     2802.01
> 

After I ran the test, I looked closer at the elapsed times and it was
due to a bug in the test setup itself. The tlbflush tests will need to
be rerun but ebizzy still has the problem where threads see very
different performance.

-- 
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>

  reply	other threads:[~2013-12-15 16:17 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-13 20:01 Mel Gorman
2013-12-13 20:01 ` [PATCH 1/4] x86: mm: Clean up inconsistencies when flushing TLB ranges Mel Gorman
2013-12-13 20:01 ` [PATCH 2/4] x86: mm: Account for TLB flushes only when debugging Mel Gorman
2013-12-13 20:01 ` [PATCH 3/4] x86: mm: Change tlb_flushall_shift for IvyBridge Mel Gorman
2013-12-13 20:01 ` [PATCH 4/4] x86: mm: Eliminate redundant page table walk during TLB range flushing Mel Gorman
2013-12-13 21:16 ` [PATCH 0/4] Fix ebizzy performance regression due to X86 TLB range flush v2 Linus Torvalds
2013-12-13 22:38   ` H. Peter Anvin
2013-12-16 10:39     ` Mel Gorman
2013-12-16 17:17       ` Linus Torvalds
2013-12-17  9:55         ` Mel Gorman
2013-12-15 15:55   ` Mel Gorman
2013-12-15 16:17     ` Mel Gorman [this message]
2013-12-15 18:34     ` Linus Torvalds
2013-12-16 11:16       ` Mel Gorman
2013-12-16 10:24     ` Ingo Molnar
2013-12-16 12:59       ` Mel Gorman
2013-12-16 13:44         ` Ingo Molnar
2013-12-17  9:21           ` Mel Gorman
2013-12-17  9:26             ` Peter Zijlstra
2013-12-17 11:00             ` Ingo Molnar
2013-12-17 14:32               ` Mel Gorman
2013-12-17 14:42                 ` Ingo Molnar
2013-12-17 17:54                   ` Mel Gorman
2013-12-18 10:24                     ` Ingo Molnar
2013-12-19 14:24               ` Mel Gorman
2013-12-19 16:49                 ` Ingo Molnar
2013-12-20 11:13                   ` Mel Gorman
2013-12-20 11:18                     ` Ingo Molnar
2013-12-20 12:00                       ` Mel Gorman
2013-12-20 12:20                         ` Ingo Molnar
2013-12-20 13:55                           ` Mel Gorman
2013-12-18  7:28 ` Fengguang Wu
2013-12-19 14:34   ` Mel Gorman
2013-12-20 15:51     ` Fengguang Wu
2013-12-20 16:44       ` Mel Gorman
2013-12-21 15:49         ` Fengguang Wu

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=20131215161754.GN11295@suse.de \
    --to=mgorman@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=alex.shi@linaro.org \
    --cc=fengguang.wu@intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.org \
    /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