From: Peter Zijlstra <peterz@infradead.org>
To: lkp@lists.01.org
Subject: Re: [sched] 143e1e28cb4: +17.9% aim7.jobs-per-min, -9.7% hackbench.throughput
Date: Sun, 10 Aug 2014 17:05:03 +0200 [thread overview]
Message-ID: <20140810150503.GV9918@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20140810105413.GA29451@localhost>
[-- Attachment #1: Type: text/plain, Size: 758 bytes --]
On Sun, Aug 10, 2014 at 06:54:13PM +0800, Fengguang Wu wrote:
> The "brickland1/aim7/6000-page_test" is the test case part.
>
> The "TOTAL XXX" is the metric part. One test run may generate lots of
> metrics, reflecting different aspect of the system dynamics.
>
> This view may be easier to read, by grouping the metrics by test case.
Right, at least that makes more sense.
> test case: brickland1/aim7/6000-page_test
Ok, so next question, what is a brickland? I suspect its a machine of
sorts, seeing how some others had wsm in that part of the test. Now I
know what a westmere is, but I've never heard of a brickland.
Please describe the machine, this is a topology patch, so we need to
know the topology of the affected machines.
[-- Attachment #2: attachment.sig --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Peter Zijlstra <peterz@infradead.org>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Vincent Guittot <vincent.guittot@linaro.org>,
Dave Hansen <dave.hansen@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
lkp@01.org, Ingo Molnar <mingo@kernel.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Preeti U Murthy <preeti@linux.vnet.ibm.com>
Subject: Re: [sched] 143e1e28cb4: +17.9% aim7.jobs-per-min, -9.7% hackbench.throughput
Date: Sun, 10 Aug 2014 17:05:03 +0200 [thread overview]
Message-ID: <20140810150503.GV9918@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20140810105413.GA29451@localhost>
[-- Attachment #1: Type: text/plain, Size: 758 bytes --]
On Sun, Aug 10, 2014 at 06:54:13PM +0800, Fengguang Wu wrote:
> The "brickland1/aim7/6000-page_test" is the test case part.
>
> The "TOTAL XXX" is the metric part. One test run may generate lots of
> metrics, reflecting different aspect of the system dynamics.
>
> This view may be easier to read, by grouping the metrics by test case.
Right, at least that makes more sense.
> test case: brickland1/aim7/6000-page_test
Ok, so next question, what is a brickland? I suspect its a machine of
sorts, seeing how some others had wsm in that part of the test. Now I
know what a westmere is, but I've never heard of a brickland.
Please describe the machine, this is a topology patch, so we need to
know the topology of the affected machines.
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-08-10 15:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-10 4:41 [sched] 143e1e28cb4: +17.9% aim7.jobs-per-min, -9.7% hackbench.throughput Fengguang Wu
2014-08-10 4:41 ` Fengguang Wu
2014-08-10 7:59 ` Peter Zijlstra
2014-08-10 7:59 ` Peter Zijlstra
2014-08-10 10:54 ` Fengguang Wu
2014-08-10 10:54 ` Fengguang Wu
2014-08-10 15:05 ` Peter Zijlstra [this message]
2014-08-10 15:05 ` Peter Zijlstra
2014-08-10 15:16 ` Ingo Molnar
2014-08-10 15:16 ` Ingo Molnar
2014-08-11 1:23 ` Fengguang Wu
2014-08-11 1:23 ` Fengguang Wu
2014-08-12 14:57 ` kodiak furr
2014-08-12 14:57 ` kodiak furr
2014-08-11 13:33 ` Peter Zijlstra
2014-08-11 13:33 ` Peter Zijlstra
2014-08-12 3:59 ` Preeti U Murthy
2014-08-12 3:59 ` Preeti U Murthy
2014-08-12 6:41 ` Peter Zijlstra
2014-08-12 6:41 ` Peter Zijlstra
2014-08-12 14:30 ` Fengguang Wu
2014-08-12 14:30 ` Fengguang Wu
2014-08-25 13:47 ` Vincent Guittot
2014-08-25 13:47 ` Vincent Guittot
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=20140810150503.GV9918@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=lkp@lists.01.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 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.