Idea for new VDSO feature: a function to query whether there are tasks waiting to run on the current cpu.
I think you're misunderstanding. Every spin for which you don't get the lock is wasted cpu cycles. Scheduler is irrelevant.
-
-
If there was nothing else that wanted to use those cycles, no big deal. But if there was, you've incurred a cost.
-
Re: "messing with scheduling", spinning at all is messing with scheduling. The default, polite action would be to always futex_wait.
-
Spinning is "I don't have anything to do yet, but let's trick the scheduler so it doesn't let someone else have my cpu time".
-
you say 'trick the scheduler', I say 'sleeping ruins all latency guarantees'.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.