[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <D7C42C27E6CB1E4D8CBDF2F81EA92A26034598724F@azsmsx501.amr.corp.intel.com>
Date: Mon, 27 Apr 2009 11:38:08 -0700
From: "Styner, Douglas W" <douglas.w.styner@...el.com>
To: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"oprofile-list@...ts.sf.net" <oprofile-list@...ts.sf.net>
CC: "Ma, Chinang" <chinang.ma@...el.com>,
Andi Kleen <andi@...stfloor.org>,
"willy@...ux.intel.com" <willy@...ux.intel.com>
Subject: Discrepancies between Oprofile and vmstat
We are using an OLTP-type workload on a fully saturated system and have begun seeing a discrepancy between the output of oprofile and vmstat on upstream kernels that was first seen with the 2.6.27 kernel.
Workload:
OLTP database workload using QLogic FC cards with MSI-X enabled doing ~50,000 IOPS
Oprofile (v0.9.3) collection methodology:
opcontrol --init
opcontrol --vmlinux=/usr/src/linux-`uname -r`/vmlinux
opcontrol -e=CPU_CLK_UNHALTED:80000 -e=LLC_MISSES:6000
opcontrol --start-daemon
sleep 5
opcontrol --start
sleep 60
opcontrol --stop
opcontrol --save=$1
opcontrol --deinit
Function classification:
Modules vmlinux and *.ko = kernel, all others = user.
Results (2.6.30-rc3 kernel):
vmstat reports ~75% user, 25% kernel
oprofile reports 70.3808% user, 29.6142% kernel
Using another profiling tool to confirm, we see 74.784% user, 25.174% kernel.
Doug Styner
douglas.w.styner@...el.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists