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
| ||
|
Message-ID: <044424e924967a1c93649812b6e1670c8c37fce4.camel@intel.com> Date: Sun, 27 Nov 2022 00:26:09 +0800 From: Zhang Rui <rui.zhang@...el.com> To: Doug Smythies <dsmythies@...us.net>, 'Kajetan Puchalski' <kajetan.puchalski@....com>, rafael@...nel.org Cc: daniel.lezcano@...aro.org, lukasz.luba@....com, Dietmar.Eggemann@....com, yu.chen.surf@...il.com, linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [RFC PATCH v4 0/2] cpuidle: teo: Introduce util-awareness On Wed, 2022-11-23 at 20:08 -0800, Doug Smythies wrote: > On 2022.11.21 04:23 Kajetan Puchalski wrote: > > > Hi Rafael, > > > > On Wed, Nov 02, 2022 at 03:28:06PM +0000, Kajetan Puchalski wrote: > > > > [...] > > > > > v3 -> v4: > > > - remove the chunk of code skipping metrics updates when the CPU > > > was utilized > > > - include new test results and more benchmarks in the cover > > > letter > > > > [...] > > > > It's been some time so I just wanted to bump this, what do you > > think > > about this v4? Doug has already tested it, resuls for his machine > > are > > attached to the v3 thread. > > Hi All, > > I continued to test this and included the proposed ladder idle > governor in my continued testing. > (Which is why I added Rui as an addressee) Hi, Doug, Really appreciated your testing data on this. I have some dumb questions and I need your help so that I can better understand some of the graphs. :) > However, I ran out of time. Here is what I have: > > Kernel: 6.1-rc3 and with patch sets > Processor: Intel(R) Core(TM) i5-10600K CPU @ 4.10GHz > CPU scaling driver: intel_cpufreq > HWP disabled. > Unless otherwsie stated, performance CPU scaling govenor. > > Legend: > teo: the current teo idle governor > util-v4: the RFC utilization teo patch set version 4. > menu: the menu idle governor > ladder-old: the current ladder idle governor > ladder: the RFC ladder patchset. > > Workflow: shell-intensive serialized workloads. > Variable: PIDs per second. > Note: Single threaded. > Master reference: forced CPU affinity to 1 CPU. > Performance Results: > http://smythies.com/~doug/linux/idle/teo-util/graphs/pids-perf.png > Schedutil Results: > http://smythies.com/~doug/linux/idle/teo-util/graphs/pids-su.png what does 1cpu mean? > > Workflow: sleeping ebizzy 128 threads. > Variable: interval (uSecs). > Performance Results: > http://smythies.com/~doug/linux/idle/teo-util/graphs/ebizzy-128-perf.png > Performance power and idle data: > http://smythies.com/~doug/linux/idle/teo-util/ebizzy/perf/ for the "Idle state 0/1/2/3 was too deep" graphs, may I know how you assert that an idle state is too deep/shallow? thanks, rui
Powered by blists - more mailing lists