| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 9 Feb 2015 10:27:35 +0100 From: Peter Zijlstra <peterz@...radead.org> To: huang ying <huang.ying.caritas@...il.com> Cc: Huang Ying <ying.huang@...el.com>, Ingo Molnar <mingo@...nel.org>, LKML <linux-kernel@...r.kernel.org>, LKP ML <lkp@...org>, "Wu, Fengguang" <fengguang.wu@...el.com> Subject: Re: [LKP] [sched/core] 9edfbfed3f5: +88.2% hackbench.time.involuntary_context_switches On Mon, Feb 09, 2015 at 04:47:07PM +0800, huang ying wrote: > There are no distinguishable difference between the parent and the child > for hackbench throughput number. > > Usually you will not consider statistics such as involuntary context > switches? Only if there's a 'problem' with the primary performance metric (total runtime in case of hackbench). Once the primary metric shifts, you go look at what the cause of this change might be, at that point things like # context switches etc.. are interesting. As long as the primary performance metric is stable, meh. As such; I would suggest _always_ reporting the primary metric for each benchmark, preferably on top and not hidden somewhere in the mass of numbers. I now had to very carefully waste a few minutes of my time reading those numbers to see if there was anything useful in; there wasn't. -- 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