New Patches Aim To Optimize Context Switching With Two Improvements

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • ayumu
    replied
    Still dogshit slow next to seL4's context switch.

    Leave a comment:


  • coder
    replied
    Originally posted by intelfx View Post
    I'm not sure how this warning (in essence an internal consistency assertion in the TLB management code) would aid in "catching early" any kind of a high-level scheduler logic bug?
    Isn't it essentially informing you that you're context-switching to/from the same core? Someone clearly thought it was a useful check to have, at one point in time. Maybe it's now redundant with a similar check at a higher level, but it seems like you'd want to have such a sanity-check to be sure the scheduler isn't generating a bunch of unnecessary/nop context switches.

    Leave a comment:


  • intelfx
    replied
    Originally posted by coder View Post
    Heh, a couple years from now, someone will probably discover a performance-robbing scheduler bug that's context-switching lots of threads on the same core, and it will turn out that this warning could've caught it early. Especially with people experimenting with sched_ext, we will want such warnings.
    I'm not sure how this warning (in essence an internal consistency assertion in the TLB management code) would aid in "catching early" any kind of a high-level scheduler logic bug?

    Leave a comment:


  • coder
    replied
    Originally posted by Rik van Riel
    This warning never ever seems to fire, even on a very large fleet, so it may be best to hide that behind CONFIG_DEBUG_VM. With the web server workload, this is also about 17% of switch_mm_irqs_off."
    Heh, a couple years from now, someone will probably discover a performance-robbing scheduler bug that's context-switching lots of threads on the same core, and it will turn out that this warning could've caught it early. Especially with people experimenting with sched_ext, we will want such warnings.

    Now, I'm not saying to leave it always enabled. However, I wouldn't hide it behind a config option that's almost never used or that someone wouldn't naturally know to use, while tinkering with schedulers.

    Leave a comment:


  • Errinwright
    replied
    Good stuff

    Leave a comment:


  • New Patches Aim To Optimize Context Switching With Two Improvements

    Phoronix: New Patches Aim To Optimize Context Switching With Two Improvements

    A set of Friday night patches provide for some exciting context switching optimizations to the Linux kernel...

    Phoronix, Linux Hardware Reviews, Linux hardware benchmarks, Linux server benchmarks, Linux benchmarking, Desktop Linux, Linux performance, Open Source graphics, Linux How To, Ubuntu benchmarks, Ubuntu hardware, Phoronix Test Suite
Working...
X