Would anyone who benefits from preempt=full
be able to retest with preempt=voluntary
?
I would like to know if your kernel is reporting any blockages in:
journalctl -b0 | grep workqueue
or
journalctl -b0 | grep 'hogged CPU'
Would anyone who benefits from preempt=full
be able to retest with preempt=voluntary
?
I would like to know if your kernel is reporting any blockages in:
journalctl -b0 | grep workqueue
or
journalctl -b0 | grep 'hogged CPU'
My Kernel settings look liike this, should I remove all of that and only leave the preempt for the test?
GRUB_CMDLINE_LINUX_DEFAULT=“mitigations=off nvidia-drm.modeset=1 ibt=off split_lock_detect=off split_lock_mitigate=0 nokaslr”
GRUB_CMDLINE_LINUX=“vdso=0 ignore_rlimit_data nvidia-drm.modeset=1 sched_migration_cost=512 pci=nommconf preempt=voluntary threadirqs”
I am asking because I have tested for almost 2 hours now. 3 Games, handbrake video work, KDenlive video work. Nothing has shown yet using the 2 commands you posted.
For example:
Same performance. Same for Kdenlive, Handbrake, google chrome, cyperpunk, gta5, the gpu recording tool.
Thanks, that’s probably enough testing. I was just hopeful it would report something after my own desktop reported such messages yesterday (about legacy framebuffer code in the kernel which we know is slow and not relevant to hardware acceleration).