A bit of history I’ve been diving into the Linux kernel scheduler recently. To give a short brief introduction to scheduling, imagine a single CPU single core system. The operating system all…

"The min_granularity setting was renamed to base_slice in this commit in v6 kernel.

The comment says it scales with CPU count and the comment is incorrect. I wonder whether kernel developers are aware of that mistake as they are rewriting the scheduler!

  • Official comments in the code says it’s scaling with log2(1+cores) but it doesn’t.
  • All the comments in the code are incorrect.
  • Official documentation and man pages are incorrect.
  • Every blog article, stack overflow answer and guide ever published about the scheduler is incorrect."
  • h3ndrik@feddit.de
    19·
    10 months ago

    Isn’t there quite some information missing? Which scheduler is affected? What are the are the exact consequences since we’re talking about latency in the first part of the article. Did it affect the AMD Epyc processors that run all the VPS?

    • waigl@lemmy.worldEnglish
      7·
      10 months ago

      Nothing is affected. The headline is largely bullshit. A minor optimization for high core-count systems did not go as far as originally planned, and that may or may not have made a barely noticable difference.