https://bugs.kde.org/show_bug.cgi?id=398391
--- Comment #2 from Rainer Finke <m...@rainer-finke.de> --- I found the following information. If I understand your blog post about real time priority of kwin correctly, it seems like SCHED_OTHER might not be enough? I played around with other values, but it didn't change anything fundamentaly. What would be the expected values of SCHED and Prio? $ ps -eL | grep kwin 1616 1616 tty2 00:00:01 kwin_wayland 1616 1620 tty2 00:00:00 kwin_wayla:cs0 1616 1621 tty2 00:00:00 kwin_wa:disk$0 1616 1622 tty2 00:00:00 kwin_wayla:sh0 1616 1623 tty2 00:00:00 kwin_wayla:sh1 1616 1624 tty2 00:00:00 kwin_wayla:sh2 1616 1625 tty2 00:00:00 kwin_wayla:sh3 1616 1626 tty2 00:00:00 kwin_wayla:sh4 1616 1627 tty2 00:00:00 kwin_wayla:sh5 1616 1628 tty2 00:00:00 kwin_wayla:sh6 1616 1629 tty2 00:00:00 kwin_wayla:sh7 1616 1630 tty2 00:00:00 kwin_wayla:sh8 1616 1631 tty2 00:00:00 kwin_wayla:sh9 1616 1632 tty2 00:00:00 kwin_wayla:sh10 1616 1633 tty2 00:00:00 kwin_wayla:sh11 1616 1634 tty2 00:00:00 kwin_way:shlo0 1616 1635 tty2 00:00:00 kwin_way:shlo1 1616 1636 tty2 00:00:00 kwin_way:shlo2 1616 1637 tty2 00:00:00 kwin_way:shlo3 1616 1638 tty2 00:00:00 kwin_way:shlo4 1616 1639 tty2 00:00:00 kwin_way:gdrv0 1616 1703 tty2 00:00:00 kwin_wayland 1679 1679 tty2 00:00:00 org_kde_kwin_xc $ chrt -p 1616 Derzeitige Scheduling-Vorschrift für PID 1616: SCHED_OTHER Derzeitige Scheduling-Priorität für PID 1616: 0 -- You are receiving this mail because: You are watching all bug changes.
