From: kodiak furr <boxerspam1@gmail.com>
To: lkp@lists.01.org
Subject: Re: [sched] 143e1e28cb4: +17.9% aim7.jobs-per-min, -9.7% hackbench.throughput
Date: Tue, 12 Aug 2014 09:57:28 -0500 [thread overview]
Message-ID: <53ea2b9a.a7d7b60a.4971.ffffda2c@mx.google.com> (raw)
In-Reply-To: <20140811012340.GA6593@localhost>
[-- Attachment #1: Type: text/plain, Size: 6678 bytes --]
.
Sent using Boxer
On Aug 10, 2014 8:23 PM, Fengguang Wu <fengguang.wu@intel.com> wrote:
>
> On Sun, Aug 10, 2014 at 05:05:03PM +0200, Peter Zijlstra wrote:
> > 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.
>
> As Ingo says, it's the "Brickland" platform with "Ivy Bridge-EX" CPU.
>
> Sorry this part can be improved -- I'll add description of the test
> boxes in future reports.
>
> > Please describe the machine, this is a topology patch, so we need to
> > know the topology of the affected machines.
>
> Here they are. If you need more (or less) information (now and future),
> please let me know.
>
> brickland1: Brickland Ivy Bridge-EX
> Memory: 128G
>
> brickland3: Brickland Ivy Bridge-EX
> Memory: 512G
> Architecture: x86_64
> CPU op-mode(s): 32-bit, 64-bit
> Byte Order: Little Endian
> CPU(s): 120
> On-line CPU(s) list: 0-119
> Thread(s) per core: 2
> Core(s) per socket: 15
> Socket(s): 4
> NUMA node(s): 4
> Vendor ID: GenuineIntel
> CPU family: 6
> Model: 62
> Stepping: 7
> CPU MHz: 3192.875
> BogoMIPS: 5593.49
> Virtualization: VT-x
> L1d cache: 32K
> L1i cache: 32K
> L2 cache: 256K
> L3 cache: 38400K
> NUMA node0 CPU(s): 0-14,60-74
> NUMA node1 CPU(s): 15-29,75-89
> NUMA node2 CPU(s): 30-44,90-104
> NUMA node3 CPU(s): 45-59,105-119
>
> lkp-snb01: Sandy Bridge-EP
> Memory: 32G
> Architecture: x86_64
> CPU op-mode(s): 32-bit, 64-bit
> Byte Order: Little Endian
> CPU(s): 32
> On-line CPU(s) list: 0-31
> Thread(s) per core: 2
> Core(s) per socket: 8
> Socket(s): 2
> NUMA node(s): 2
> Vendor ID: GenuineIntel
> CPU family: 6
> Model: 45
> Stepping: 6
> CPU MHz: 3498.820
> BogoMIPS: 5391.31
> Virtualization: VT-x
> L1d cache: 32K
> L1i cache: 32K
> L2 cache: 256K
> L3 cache: 20480K
> NUMA node0 CPU(s): 0-7,16-23
> NUMA node1 CPU(s): 8-15,24-31
>
> wsm: Westmere
> Memory: 6G
> Architecture: x86_64
> CPU op-mode(s): 32-bit, 64-bit
> Byte Order: Little Endian
> CPU(s): 12
> On-line CPU(s) list: 0-11
> Thread(s) per core: 2
> Core(s) per socket: 6
> Socket(s): 1
> NUMA node(s): 1
> Vendor ID: GenuineIntel
> CPU family: 6
> Model: 44
> Stepping: 2
> CPU MHz: 3458.000
> BogoMIPS: 6756.46
> Virtualization: VT-x
> L1d cache: 32K
> L1i cache: 32K
> L2 cache: 256K
> L3 cache: 12288K
> NUMA node0 CPU(s): 0-11
>
> lkp-nex04: Nehalem-EX
> Memory: 256G
> Architecture: x86_64
> CPU op-mode(s): 32-bit, 64-bit
> Byte Order: Little Endian
> CPU(s): 64
> On-line CPU(s) list: 0-63
> Thread(s) per core: 2
> Core(s) per socket: 8
> Socket(s): 4
> NUMA node(s): 4
> Vendor ID: GenuineIntel
> CPU family: 6
> Model: 46
> Stepping: 6
> CPU MHz: 2262.000
> BogoMIPS: 4521.30
> Virtualization: VT-x
> L1d cache: 32K
> L1i cache: 32K
> L2 cache: 256K
> L3 cache: 24576K
> NUMA node0 CPU(s): 0-7,32-39
> NUMA node1 CPU(s): 8-15,40-47
> NUMA node2 CPU(s): 16-23,48-55
> NUMA node3 CPU(s): 24-31,56-63
>
> nhm4: Nehalem
> Memory: 4G
> Architecture: x86_64
> CPU op-mode(s): 32-bit, 64-bit
> Byte Order: Little Endian
> CPU(s): 8
> On-line CPU(s) list: 0-7
> Thread(s) per core: 2
> Core(s) per socket: 4
> Socket(s): 1
> NUMA node(s): 1
> Vendor ID: GenuineIntel
> CPU family: 6
> Model: 26
> Stepping: 4
> CPU MHz: 3193.000
> BogoMIPS: 6400.40
> Virtualization: VT-x
> L1d cache: 32K
> L1i cache: 32K
> L2 cache: 256K
> L3 cache: 8192K
> NUMA node0 CPU(s): 0-7
>
> Thanks,
> Fengguang
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo(a)vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
WARNING: multiple messages have this Message-ID (diff)
From: kodiak furr <boxerspam1@gmail.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: lkp@01.org, Vincent Guittot <vincent.guittot@linaro.org>,
Dave Hansen <dave.hansen@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Preeti U Murthy <preeti@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [sched] 143e1e28cb4: +17.9% aim7.jobs-per-min, -9.7% hackbench.throughput
Date: Tue, 12 Aug 2014 09:57:28 -0500 [thread overview]
Message-ID: <53ea2b9a.a7d7b60a.4971.ffffda2c@mx.google.com> (raw)
In-Reply-To: <20140811012340.GA6593@localhost>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 6665 bytes --]
.
Sent using Boxer
On Aug 10, 2014 8:23 PM, Fengguang Wu <fengguang.wu@intel.com> wrote:
>
> On Sun, Aug 10, 2014 at 05:05:03PM +0200, Peter Zijlstra wrote:
> > 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.
>
> As Ingo says, it's the "Brickland" platform with "Ivy Bridge-EX" CPU.
>
> Sorry this part can be improved -- I'll add description of the test
> boxes in future reports.
>
> > Please describe the machine, this is a topology patch, so we need to
> > know the topology of the affected machines.
>
> Here they are. If you need more (or less) information (now and future),
> please let me know.
>
> brickland1: Brickland Ivy Bridge-EX
> Memory: 128G
>
> brickland3: Brickland Ivy Bridge-EX
> Memory: 512G
> Architecture:Â Â Â Â Â Â Â Â Â x86_64
> CPU op-mode(s):Â Â Â Â Â Â Â 32-bit, 64-bit
> Byte Order:Â Â Â Â Â Â Â Â Â Â Â Little Endian
> CPU(s):Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 120
> On-line CPU(s) list:Â Â 0-119
> Thread(s) per core:Â Â Â 2
> Core(s) per socket:Â Â Â 15
> Socket(s):Â Â Â Â Â Â Â Â Â Â Â Â 4
> NUMA node(s):Â Â Â Â Â Â Â Â Â 4
> Vendor ID:Â Â Â Â Â Â Â Â Â Â Â Â GenuineIntel
> CPU family:Â Â Â Â Â Â Â Â Â Â Â 6
> Model:Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 62
> Stepping:Â Â Â Â Â Â Â Â Â Â Â Â Â 7
> CPU MHz:Â Â Â Â Â Â Â Â Â Â Â Â Â Â 3192.875
> BogoMIPS:Â Â Â Â Â Â Â Â Â Â Â Â Â 5593.49
> Virtualization:Â Â Â Â Â Â Â VT-x
> L1d cache:Â Â Â Â Â Â Â Â Â Â Â Â 32K
> L1i cache:Â Â Â Â Â Â Â Â Â Â Â Â 32K
> L2 cache:Â Â Â Â Â Â Â Â Â Â Â Â Â 256K
> L3 cache:Â Â Â Â Â Â Â Â Â Â Â Â Â 38400K
> NUMA node0 CPU(s):Â Â Â Â 0-14,60-74
> NUMA node1 CPU(s):Â Â Â Â 15-29,75-89
> NUMA node2 CPU(s):Â Â Â Â 30-44,90-104
> NUMA node3 CPU(s):Â Â Â Â 45-59,105-119
>
> lkp-snb01: Sandy Bridge-EP
> Memory: 32G
> Architecture:Â Â Â Â Â Â Â Â Â x86_64
> CPU op-mode(s):Â Â Â Â Â Â Â 32-bit, 64-bit
> Byte Order:Â Â Â Â Â Â Â Â Â Â Â Little Endian
> CPU(s):Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 32
> On-line CPU(s) list:Â Â 0-31
> Thread(s) per core:Â Â Â 2
> Core(s) per socket:Â Â Â 8
> Socket(s):Â Â Â Â Â Â Â Â Â Â Â Â 2
> NUMA node(s):Â Â Â Â Â Â Â Â Â 2
> Vendor ID:Â Â Â Â Â Â Â Â Â Â Â Â GenuineIntel
> CPU family:Â Â Â Â Â Â Â Â Â Â Â 6
> Model:Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 45
> Stepping:Â Â Â Â Â Â Â Â Â Â Â Â Â 6
> CPU MHz:Â Â Â Â Â Â Â Â Â Â Â Â Â Â 3498.820
> BogoMIPS:Â Â Â Â Â Â Â Â Â Â Â Â Â 5391.31
> Virtualization:Â Â Â Â Â Â Â VT-x
> L1d cache:Â Â Â Â Â Â Â Â Â Â Â Â 32K
> L1i cache:Â Â Â Â Â Â Â Â Â Â Â Â 32K
> L2 cache:Â Â Â Â Â Â Â Â Â Â Â Â Â 256K
> L3 cache:Â Â Â Â Â Â Â Â Â Â Â Â Â 20480K
> NUMA node0 CPU(s):Â Â Â Â 0-7,16-23
> NUMA node1 CPU(s):Â Â Â Â 8-15,24-31
>
> wsm: Westmere
> Memory: 6G
> Architecture:Â Â Â Â Â Â Â Â Â x86_64
> CPU op-mode(s):Â Â Â Â Â Â Â 32-bit, 64-bit
> Byte Order:Â Â Â Â Â Â Â Â Â Â Â Little Endian
> CPU(s):Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 12
> On-line CPU(s) list:Â Â 0-11
> Thread(s) per core:Â Â Â 2
> Core(s) per socket:Â Â Â 6
> Socket(s):Â Â Â Â Â Â Â Â Â Â Â Â 1
> NUMA node(s):Â Â Â Â Â Â Â Â Â 1
> Vendor ID:Â Â Â Â Â Â Â Â Â Â Â Â GenuineIntel
> CPU family:Â Â Â Â Â Â Â Â Â Â Â 6
> Model:Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 44
> Stepping:Â Â Â Â Â Â Â Â Â Â Â Â Â 2
> CPU MHz:Â Â Â Â Â Â Â Â Â Â Â Â Â Â 3458.000
> BogoMIPS:Â Â Â Â Â Â Â Â Â Â Â Â Â 6756.46
> Virtualization:Â Â Â Â Â Â Â VT-x
> L1d cache:Â Â Â Â Â Â Â Â Â Â Â Â 32K
> L1i cache:Â Â Â Â Â Â Â Â Â Â Â Â 32K
> L2 cache:Â Â Â Â Â Â Â Â Â Â Â Â Â 256K
> L3 cache:Â Â Â Â Â Â Â Â Â Â Â Â Â 12288K
> NUMA node0 CPU(s):Â Â Â Â 0-11
>
> lkp-nex04: Nehalem-EX
> Memory: 256G
> Architecture:Â Â Â Â Â Â Â Â Â x86_64
> CPU op-mode(s):Â Â Â Â Â Â Â 32-bit, 64-bit
> Byte Order:Â Â Â Â Â Â Â Â Â Â Â Little Endian
> CPU(s):Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 64
> On-line CPU(s) list:Â Â 0-63
> Thread(s) per core:Â Â Â 2
> Core(s) per socket:Â Â Â 8
> Socket(s):Â Â Â Â Â Â Â Â Â Â Â Â 4
> NUMA node(s):Â Â Â Â Â Â Â Â Â 4
> Vendor ID:Â Â Â Â Â Â Â Â Â Â Â Â GenuineIntel
> CPU family:Â Â Â Â Â Â Â Â Â Â Â 6
> Model:Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 46
> Stepping:Â Â Â Â Â Â Â Â Â Â Â Â Â 6
> CPU MHz:Â Â Â Â Â Â Â Â Â Â Â Â Â Â 2262.000
> BogoMIPS:Â Â Â Â Â Â Â Â Â Â Â Â Â 4521.30
> Virtualization:Â Â Â Â Â Â Â VT-x
> L1d cache:Â Â Â Â Â Â Â Â Â Â Â Â 32K
> L1i cache:Â Â Â Â Â Â Â Â Â Â Â Â 32K
> L2 cache:Â Â Â Â Â Â Â Â Â Â Â Â Â 256K
> L3 cache:Â Â Â Â Â Â Â Â Â Â Â Â Â 24576K
> NUMA node0 CPU(s):Â Â Â Â 0-7,32-39
> NUMA node1 CPU(s):Â Â Â Â 8-15,40-47
> NUMA node2 CPU(s):Â Â Â Â 16-23,48-55
> NUMA node3 CPU(s):Â Â Â Â 24-31,56-63
>
> nhm4: Nehalem
> Memory: 4G
> Architecture:Â Â Â Â Â Â Â Â Â x86_64
> CPU op-mode(s):Â Â Â Â Â Â Â 32-bit, 64-bit
> Byte Order:Â Â Â Â Â Â Â Â Â Â Â Little Endian
> CPU(s):Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 8
> On-line CPU(s) list:Â Â 0-7
> Thread(s) per core:Â Â Â 2
> Core(s) per socket:Â Â Â 4
> Socket(s):Â Â Â Â Â Â Â Â Â Â Â Â 1
> NUMA node(s):Â Â Â Â Â Â Â Â Â 1
> Vendor ID:Â Â Â Â Â Â Â Â Â Â Â Â GenuineIntel
> CPU family:Â Â Â Â Â Â Â Â Â Â Â 6
> Model:Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 26
> Stepping:Â Â Â Â Â Â Â Â Â Â Â Â Â 4
> CPU MHz:Â Â Â Â Â Â Â Â Â Â Â Â Â Â 3193.000
> BogoMIPS:Â Â Â Â Â Â Â Â Â Â Â Â Â 6400.40
> Virtualization:Â Â Â Â Â Â Â VT-x
> L1d cache:Â Â Â Â Â Â Â Â Â Â Â Â 32K
> L1i cache:Â Â Â Â Â Â Â Â Â Â Â Â 32K
> L2 cache:Â Â Â Â Â Â Â Â Â Â Â Â Â 256K
> L3 cache:Â Â Â Â Â Â Â Â Â Â Â Â Â 8192K
> NUMA node0 CPU(s):Â Â Â Â 0-7
>
> Thanks,
> Fengguang
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2014-08-12 14:57 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
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 [this message]
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=53ea2b9a.a7d7b60a.4971.ffffda2c@mx.google.com \
--to=boxerspam1@gmail.com \
--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.