3 ms·
You have to see it as a way to enable applications to inform and steer the kernel towards their scheduling policies. For instance, one of these policies could v
by zekrioca 5y ago
You have to see it as a way to enable applications to inform and steer the kernel towards their scheduling policies. For instance, one of these policies could very well be the current Completely Fair Scheduler (CFS) Linux already uses[1]. And alternatively, you can have any other policy that reduces context switching, if this is your target.
[1] https://en.wikipedia.org/wiki/Completely_Fair_Scheduler https://en.wikipedia.org/wiki/Completely_Fair_Scheduler
- delusional 5y agoI think he's asking if implementing CFS in userspace, with no other changes, wouldn't in itself cause more context switches. I don't understand how your comment addresses that point. Sure you could implement something different, but you could do that without the userspace component too, and adding the userspace component is pretty expensive.
- lallysingh 5y agoNope, you want information to go from userspace to scheduling decisions. Where the code resides is implementation. Having userspace tell the scheduler what it needs avoids the round trip if it applies to more than one scheduling decision.