From: Fengguang Wu <fengguang.wu@intel.com>
To: lkp@lists.01.org
Subject: [ACPI / hotplug / PCI] 1b360f44d00: -80.9% vm-scalability.stddev
Date: Wed, 05 Mar 2014 16:23:36 +0800 [thread overview]
Message-ID: <20140305082336.GD17109@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 2306 bytes --]
Hi Rafael,
I don't know why but we are glad to find the below changes on commit
1b360f44d009059e446532f29c1a889951e72667 ("ACPI / hotplug / PCI: Fix bridge removal race in handle_hotplug_event()")
test case: brickland2/micro/vm-scalability/300s-anon-r-rand-mt
d42f5da23400833 1b360f44d009059e446532f29
--------------- -------------------------
3.54 ~164% -80.9% 0.68 ~37% TOTAL vm-scalability.stddev
14177 ~ 7% -22.1% 11040 ~ 7% TOTAL numa-meminfo.node0.SReclaimable
3543 ~ 7% -22.1% 2759 ~ 7% TOTAL numa-vmstat.node0.nr_slab_reclaimable
776196 ~ 6% -10.0% 698893 ~ 5% TOTAL numa-numastat.node2.local_node
776196 ~ 6% -10.0% 698894 ~ 5% TOTAL numa-numastat.node2.numa_hit
The ~XX% numbers are stddev percent.
The [+-]XX% is change percent.
The below graph shows all samples collected during the bisect
[*] bisect-good
[O] bisect-bad ("bad" in the sense of bisect)
In which you can see the stableness of the change and bisect.
vm-scalability.stddev
16 ++--------------------------------------------------------------------+
| * |
14 ++ : |
12 ++ : |
| :: |
10 ++ :: |
| :: |
8 ++ :: |
| : : |
6 ++ * : : |
4 ++ * * :: : : |
| +: : + * : : : : |
2 ++*. *. .* : : * .*. + : : : .* : : |
|+ * + * *. .* O *.*.*. .** O.**.O.* O: *.O.* O OO.* + : *.|
0 O+O-OO-O-O-O-OO-O-O---OO-O-O-O-OO-O---OO-*-O---OO-*-O------O-O-*-*----*
Thanks,
Fengguang
WARNING: multiple messages have this Message-ID (diff)
From: Fengguang Wu <fengguang.wu@intel.com>
To: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>, lkp@01.org
Subject: [ACPI / hotplug / PCI] 1b360f44d00: -80.9% vm-scalability.stddev
Date: Wed, 5 Mar 2014 16:23:36 +0800 [thread overview]
Message-ID: <20140305082336.GD17109@localhost> (raw)
Hi Rafael,
I don't know why but we are glad to find the below changes on commit
1b360f44d009059e446532f29c1a889951e72667 ("ACPI / hotplug / PCI: Fix bridge removal race in handle_hotplug_event()")
test case: brickland2/micro/vm-scalability/300s-anon-r-rand-mt
d42f5da23400833 1b360f44d009059e446532f29
--------------- -------------------------
3.54 ~164% -80.9% 0.68 ~37% TOTAL vm-scalability.stddev
14177 ~ 7% -22.1% 11040 ~ 7% TOTAL numa-meminfo.node0.SReclaimable
3543 ~ 7% -22.1% 2759 ~ 7% TOTAL numa-vmstat.node0.nr_slab_reclaimable
776196 ~ 6% -10.0% 698893 ~ 5% TOTAL numa-numastat.node2.local_node
776196 ~ 6% -10.0% 698894 ~ 5% TOTAL numa-numastat.node2.numa_hit
The ~XX% numbers are stddev percent.
The [+-]XX% is change percent.
The below graph shows all samples collected during the bisect
[*] bisect-good
[O] bisect-bad ("bad" in the sense of bisect)
In which you can see the stableness of the change and bisect.
vm-scalability.stddev
16 ++--------------------------------------------------------------------+
| * |
14 ++ : |
12 ++ : |
| :: |
10 ++ :: |
| :: |
8 ++ :: |
| : : |
6 ++ * : : |
4 ++ * * :: : : |
| +: : + * : : : : |
2 ++*. *. .* : : * .*. + : : : .* : : |
|+ * + * *. .* O *.*.*. .** O.**.O.* O: *.O.* O OO.* + : *.|
0 O+O-OO-O-O-O-OO-O-O---OO-O-O-O-OO-O---OO-*-O---OO-*-O------O-O-*-*----*
Thanks,
Fengguang
next reply other threads:[~2014-03-05 8:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 8:23 Fengguang Wu [this message]
2014-03-05 8:23 ` [ACPI / hotplug / PCI] 1b360f44d00: -80.9% vm-scalability.stddev Fengguang Wu
2014-03-05 12:58 ` Rafael J. Wysocki
2014-03-05 12:58 ` Rafael J. Wysocki
2014-03-05 12:49 ` Fengguang Wu
2014-03-05 12: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=20140305082336.GD17109@localhost \
--to=fengguang.wu@intel.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.