Conversation
rostedt

Steven Rostedt

Edited 4 months ago
"And you get a scheduler, and you get a scheduler, and you get a scheduler"

[ stolen from a colleague ]

3
6
9
Aissen@social.treehouse.systems

Anisse

Reply to @rostedt
Edited 4 months ago

@rostedt

0
3
0
andree@hometech.social

Andree

Reply to @rostedt

@rostedt derived from xkcd.com/927 :

1
0
1
codonell@fosstodon.org

Carlos O'Donell

Reply to @rostedt

@rostedt "And you get a malloc, and you get a malloc, and you get a malloc"

[ stolen from Steven ]

I'm eagerly waiting for downstream policy on this 😃

0
0
0
rostedt

Steven Rostedt

Reply to @andree@hometech.social

@andree Actually, the issue is the opposite. What we have is a one size scheduler that fits everyone. But I think it’s more like all season tires. Where they suck in all seasons, but suck equally. The issue I found most frustrating with making changes to the scheduler, is that you may make a change that helps your specific workload, but will cause regressions in someone else’s workload, and your change much be reverted. Now you are stuck with either our of tree patches, or your workflow suffers.

I’m not a big fan of BPF, but I have been a long advocate for pluggable schedulers. My preference would have been true kernel modules, or config options (like file systems), as BPF programs are IMO harder to collaborate on.

1
0
1
andree@hometech.social

Andree

Reply to @rostedt

@rostedt thanks for the clarification

0
0
0
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: