I’m not smart enough to verify the accuracy of this claim, nor exactly what the implications are, but it seems like it might improve performance if fixed.

  • Papamousse@beehaw.org
    link
    fedilink
    arrow-up
    23
    arrow-down
    1
    ·
    1 year ago

    Title bullshit, we have multicore machine for years, I can guarantee you this had about no impact else people running Xeon or Threadripper would have saw it at first try 15 years ago.

    This looks like to have an impact on the scheduler but not on how many cores are used.

    • The Doctor@beehaw.org
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 year ago

      I agree. Some of the Linux servers I used to run at work in the early 00’s were 12 to 16 core monsters (for the time) and the kernel didn’t even blink.

  • madasi@lemmy.dbzer0.comOP
    link
    fedilink
    arrow-up
    8
    ·
    1 year ago

    I took the title from the link, which doesn’t exactly match the title on the page. That’s why one says 20 years and the other says 15 years.

  • Pantherina@feddit.de
    link
    fedilink
    arrow-up
    7
    arrow-down
    1
    ·
    1 year ago

    Heard of that, because you know, a core Duo was a thing. They didnt think anything bigger was possible, some time in the past. But afaik thats pretty old news

  • merthyr1831@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    Would’ve been nice of them to compile the kernel with a fix applied to see how much of an impact it has (though even in the post they seem to suggest that it’s not that impactful unless you run massive clusters)