Work in progress: 181,232 of 181,233 sites checked so far, more every week · updated 2 Nov 2026Missing a blog? Tell us

Top all-time · #11403

C

Con Kolivas

Personal blog · ck-hack.blogspot.comsystemsprogramming

Con Kolivas writes -ck hacking, a personal blog at ck-hack.blogspot.com about systems and programming. Since 2011, 7 different Hacker News readers have linked it 7 times, most often “I will have to sadly declare 5.12-ck the last of the MuQSS and -ck patches”. It is still writing: the last post was on 2026-10-19, and you can follow it by feed.

Visit the blog
7mentions?
7HN people?
2011–2022first – last linked?
Links on Hacker News per year · peak 2 in 2016

Too few sampled comments (3) to say how often HN recommends it.?

Why HN links it

Con Kolivas's blog on Linux kernel CPU scheduler work, including his out-of-tree -ck patches and the MuQSS scheduler. HN commenters cite it as background; none comment on the writing itself.

Summarised by Claude from a sample of 3 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.

A development blog of what Con Kolivas is doing with code at the moment with the emphasis on linux kernel, MuQSS, BFS and -ck.

Most-linked posts?

  1. I will have to sadly declare 5.12-ck the last of the MuQSS and -ck patches
    2 people · 2 mentions · first linked 2021-08-31

What Hacker News says?

  1. I wonder if they are discouraged by the experience of Con Kolivas[1] who proposed an alternative scheduler back in 2007. (Apparently he is still maintaining his "-ck" fork of the linux kernel[2]!) I only mention this as a historical case that has remained in my memory. Maybe Linus is willing to revisit the issue, I don't follow LKML. [1] https://en.wikipedia.org/wiki/Con_Kolivas [2] http://ck-hack.blogspot.com/2015/…

    Comment linking /2015/12/bfs-467-linux-43-ck3.html

    on “The Linux Scheduler: A Decade of Wasted Cores [pdf]”
  2. Submitted SMT/Hyperthreading, nice and scheduling policies as a story · 3 points

    HN discussion
  3. That's Con Kolivas. It wasn't merged, he maintained patches out of tree until recently[0]. A pity as latency doesn't seem like a high priority for Linux. Strictly speaking a real-time OS isn't about that though, that's about bounded latency, not low latency. [0] http://ck-hack.blogspot.com/2021/08/514-and-future-of-muqss-...

    Comment linking /2021/08/514-and-future-of-muqss-and-ck-once.html

    on “Intel energizes decades-old real-time Linux kernel project”
  4. Submitted Anatomy of a software engineer reject as a story · 3 points

    HN discussion
  5. Weird, the measurement scale they use does not jive with the scale of the knobs being tweaked. For example, `sched_cfs_bandwidth_slice_us` is adjusted by the project's `bandwidth_size` knob. The default is 5000 us, or 5 ms. But the knob they mention it being '5 us'. Same goes for scheduling latency-- its not `us`, its `ms`. And afaik, the 'sauce' used in Liquorix is MuQSS, by Con Kolivas. But the project has been pu…

    Comment linking /2021/08/514-and-future-of-muqss-and-ck-once.html

    on “Ask HN: Is there any tool for benchmarking responsiveness for Linux?”
  6. Submitted I will have to sadly declare 5.12-ck the last of the MuQSS and -ck patches as a story · 2 points

    HN discussion
  7. Submitted MuQSS – The Multiple Queue Skiplist Scheduler (BFS Evolution) as a story · 1 points

    HN discussion

Search all of HN for ck-hack.blogspot.com

Linked by the same people?