You can manually set the CPU affinity (see taskset utility) to decide the core(s) where to run your process, even if it is already running. ________________________________ From: stan via devel <devel@xxxxxxxxxxxxxxxxxxxxxxx> Sent: Monday, September 21, 2020 9:06 PM To: kernel@xxxxxxxxxxxxxxxxxxxxxxx <kernel@xxxxxxxxxxxxxxxxxxxxxxx> Cc: Development discussions related to Fedora <devel@xxxxxxxxxxxxxxxxxxxxxxx>; stan <upaitag@xxxxxxxx> Subject: System no longer distributes load to multiple cores for long running task Hi, It's been a while (6 months?) since I ran a python program that uses a 100% cpu core for hours. The last time I ran it, the task would migrate from core to core to core, every second or so. I could see it doing so in the various tops. Now, it runs on only one core, and doesn't move. This is more efficient from a computing perspective because there aren't as many task switches, but it means that the core that is running gets very hot. Since the rest of the cores are idle, I would like to switch back to the previous behavior for this reason. Can someone tell me how? Thanks. PS I'm copying devel in case this isn't a kernel issue, and also because my posts to the kernel list just seem to disappear into the ether. _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ kernel mailing list -- kernel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to kernel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@xxxxxxxxxxxxxxxxxxxxxxx
