Friday, 25 October 2019

linux-5.3-ck1, MuQSS version 0.195 for linux-5.3

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

-ck1 patches:
Git tree:
MuQSS only:
Git tree:


This is a resync from 5.2-ck1 plus the Ryzen/LLC fixes courtesy of Eduards Bezverhijs (thanks very much!) virtually unchanged. A reminder if you're new to using my patches, MuQSS performs best when in combination with the full -ck patchset as they're all complementary changes.
Sorry about the delay, I was in the thick of a project I had to complete first.

You will find that it may not completely apply to later 5.3.x kernels because of a very small change to a Makefile. It's trivial to fix, but please note my patches are always designed around 2 point releases, in this case 5.3, and I never try to resync with the many 3 point stable releases that follow.


  1. Thank you for the update.

    Note, that that the patch fails to apply against 5.3.7 at tools/objtool/Makefile, for the same reason 5.2-ck1 failed against 5.2.18.

    The patch can be again updated to apply against the latest kernel releases with the following:
    sed -i -e '/^-CFLAGS/ s,+=,:=,' -i -e '/^+CFLAGS/ s,+=,:=,' patch-5.3-ck1

  2. This comment has been removed by a blog administrator.

  3. Thank you for the update.

    I am trying to incorporate the -ck patchset into the disto I use. They have a kernel config which is generated through the use of their tooling. Do I need to manually select any kernel config options or will the patchset set what is required (for a laptop) automatically? For example something like, CONFIG_FORCE_IRQ_THREADING=y.

    A better question might be what are the necessary kernel config options for proper -ck patchset experience.


    1. The default config options are the most compatible and give you most of the experience. The IRQ threading for example very rarely causes issues which is why I don't default to having it on.

  4. Thank you for the update.

    It does not seem as this includes the patch described here: with patch posted here:

    Given i have not actually tested -ck on 5.3 yet, but since BMQ incorporates this patch with current release, i would think it is needed.

  5. patch -p1 < ../5.3-ck1/0002-Fix-Werror-build-failure-in-tools.patch
    patching file tools/objtool/Makefile
    Hunk #1 FAILED at 35.
    1 out of 1 hunk FAILED -- saving rejects to file tools/objtool/Makefile.rej

    1. Look at the first post up top...

    2. The patch is unfortunately always designed around the 2 point release, in this case 5.3. The sed script provided above by ooo (thanks!) can make it work with the latest 3 point release.

    3. OK, got it.

  6. Thank you very much.

  7. Hello there!

    First off, just want to say thank you for all the hard work you do, I use the linux-ck-skylake from the repo-ck repo on arch and it is amazing.

    One request though, and if this is the wrong place to make such a request then I apologise, but have you considered applying the fsync patchset? It's the only thing I miss from linux-zen, otherwise, yours trumps it in every way, haha

    Again, thank you so much. have a great day!

    1. You're welcome. My experience with maintaining other peoples' patches has not been that satisfactory so I prefer to only stick to patches that I've created for convenience, efficiency, familiarity, reliability, and workload.

    2. I have to agree, as fsync imo does not really have that much to do with scheduler patches. Patchsets like the fsync patches is more distro/other specific, and maintaining upgrades from Valve to this before its mainline is not really efficient.

      Andrew: You are better off trying to get distro's like Arch/Ubuntu/"insert-name-here" to default the fsync patches. TKGlitch kernel have this as an PKGBUILD option and so on.


    4. Hello all,

      Thank you so much for getting back to me so promptly, I will write this in the linux-ck forum support thread and see what can be done.

      All the best!