-
Notifications
You must be signed in to change notification settings - Fork 12
Frequency locked with ondemand
governor
#5
Comments
Hi @raykzhao Thank you for testing and debugging the scheduler. I believe that we had the same issue regarding cpus freq. with RDB before and the fix was related to the task stats and accounting. I will add a sub kconfig option under TT to allow for full tasks accounting (please see https://github.com/hamadmarri/TT-CPU-Scheduler#future-plan). It is a serious issue since the performance of the task which is running on the locked cpu with low frequency will be affected (in case if cpu freq. is not just falsely reporting some numbers while the actual cpu freq is higher). Thank you so much 👍 |
Hi @raykzhao Could you please try this fix |
Hi @hamadmarri, It seems that with this patch,
|
Ops, I am working on it. |
Hi @hamadmarri, Thank you for the patch! Both CPU frequency scaling issues with |
Hi @hamadmarri, Although |
Yes, I still have this problem. I think I am missing some load updates in one of the nohz function. I will check. Please see this update |
I am not sure if this is still relevant (Feb. 25, 2016)
I forgot to update load in the most important functions :D |
Hi @hamadmarri, With the latest patch, |
Hi @hamadmarri, I just tested the cfs with Thank you for the fix. |
Hi @hamadmarri,
I notice that with the tt-scheduler on 5.15 kernel, the lowest frequency of some CPU cores might be locked at a random frequency with the ondemand scaling governor (both with and w/o
intel_pstate
). There is no such issue with the cfs scheduler on my machine.This could be easily solved with
cpupower frequency-set -g powersave
and thencpupower frequency-set -g ondemand
. However, since I have noticed that sometimes the lowest frequency of a CPU core might be locked at e.g. turbo frequency, it would be nice to make sure that the ondemand governor can work correctly for laptops during boot without intervention. I remember one earlier version of MuQSS/PDS had the same issue so I guess this might be related to the stats.Another issue I have noticed is that, with
nohz_full
enabled for all cores except CPU0, some random CPU cores other than CPU0 might be locked at a low frequency i.e. no frequency scaling at all with theondemand
governor even under load. It seems that cfs scheduler does not have the frequency scaling issue withnohz_full
. Also I can confirm via/proc/sched_debug
that there is actually a task running on the frequency locked cores under load with the tt-scheduler.By the way, thanks for your awesome scheduler! In my daily usage on my laptop, so far my system is quite smooth and I did not notice any freezes. I am using the tt-scheduler patch on top of the vanilla kernel with some other patches (most are picked from https://github.com/sirlucjan/kernel-patches/tree/master/5.15).
The text was updated successfully, but these errors were encountered: