If you fix the issue, kindly add following tagīin/lkp install job.yaml # job file is attached in this emailĬompiler/cpufreq_governor/kconfig/mode/nr_task/rootfs/tbox_group/test/testcase/ucode: | test parameters | cpufreq_governor=performance | | test machine | 288 threads Intel(R) Xeon Phi(TM) CPU 7295 1.50GHz with 80G memory | | testcase: change | will-it-scale: will-it-scale.per_thread_ops -51.3% regression | In addition to that, the commit also has significant impact on the following tests: It builds both a process and threads based test in order to see any differences between the two. Test-description: Will It Scale takes a testcase and runs it from 1 through to n parallel copies to see if the testcase will scale.
On test machine: 288 threads Intel(R) Xeon Phi(TM) CPU 7295 1.50GHz with 80G memory To: yangerkun +Cc: Jeff Layton, LKML, Linus Torvalds, lkpįYI, we noticed a -96.6% regression of will-it-scale.per_process_ops due to commit:Ĭommit: 6d390e4b5d48ec03bb87e63cf0a2bff5f4e116da ("locks: fix a potential use-after-free problem when wakeup a waiter") 6d390e4b5d: will-it-scale.per_process_ops -96.6% regression All of help / color / mirror / Atom feed * 6d390e4b5d: will-it-scale.per_process_ops -96.6% regression 14:03 ` kernel test robot 0 siblings, 0 replies 110+ messages in threadįrom: kernel test robot 14:03 UTC ( / raw)
0 kommentar(er)
