Tuesday, 4 February 2020

linux-5.5-ck1, MuQSS version 0.198 for linux-5.5

Announcing a new -ck release, 5.5-ck1  with the latest version of the Multiple Queue Skiplist Scheduler, version 0.198. These are patches designed to improve system responsiveness and interactivity with specific emphasis on the desktop, but configurable for any workload.

linux-5.5-ck1:
-ck1 patch:
Git tree:
MuQSS only:
Download:
Git tree:
Web: http://kernel.kolivas.org
This is a resync from 5.4-ck1, with some minor tidying and fixes.

Enjoy!
お楽しみ下さい
-ck

12 comments:

  1. Thank you. Works fine so far.

    ReplyDelete
  2. Thanks for the update.

    ReplyDelete
  3. Thank you very much.

    ReplyDelete
  4. There is no doubt your scheduler is buggy on some hardware, I've tested this 'scheduler' on a thinkpad T420 on 5.4-ck it crash (kernel panic). Now on 5.5 same issue, I didn't got an asnwer from you on the 5.4 post so I do not expect one from here, but here you go same buggy behavior.

    ReplyDelete
    Replies
    1. Did you enable irq threads? They're known not to work on a lot of hardware which is why it's disabled by default.

      Delete
    2. It's also worth trying disabling runqueue sharing with the rqshare=none parameter.

      Delete
    3. I will whenever I have a chance.

      Delete
  5. Con, what are your thoughts about this commit?
    https://github.com/zen-kernel/zen-kernel/commit/d1bebeb959a56324fe436443ea2f21a8391632d9

    ReplyDelete
  6. Hey Con, thanks again for keeping it up to date. I've tested it and it's working, but there's been an ongoing issue since 5.x where the system will be working as normal but starting new applications will hang indefinitely until I end a particularly CPU heavy process. Have you noticed this?

    I'll be testing the commit vinibali posted.

    As an aside: is there a way to measure power consumption accurately on a desktop with software? I'd like to compare power consumption between kernels. Thanks again.

    ReplyDelete
    Replies
    1. I have not noticed this, but it may be unique to your hardware/software configuration. If you are using irq threads try disabling them (or vice versa.) Powertop is probably the best way to accurately gauge power consumption over short periods.

      Delete
    2. Same issue on 5.4 kernel.
      It's solved by enabling irq threads in my case.

      Delete
    3. Thanks, that did the trick.

      Delete