Talk:Brain Fuck Scheduler

From Wikipedia, the free encyclopedia
Jump to: navigation, search
WikiProject Linux (Rated Start-class, Low-importance)
WikiProject icon This article is within the scope of WikiProject Linux, a collaborative effort to improve the coverage of Linux on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
Start-Class article Start  This article has been rated as Start-Class on the project's quality scale.
 Low  This article has been rated as Low-importance on the project's importance scale.
 
WikiProject Software / Computing  (Rated Start-class, Low-importance)
WikiProject icon This article is within the scope of WikiProject Software, a collaborative effort to improve the coverage of software on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
Start-Class article Start  This article has been rated as Start-Class on the project's quality scale.
 Low  This article has been rated as Low-importance on the project's importance scale.
Taskforce icon
This article is supported by WikiProject Computing.
 

Unnamed section[edit]

So the reference for BFS is also being adopted by Google's "mainline" Android development repository is just a git tree that has experimental in the name? I think that phrase implies a bit more...

Naming[edit]

"Brain Fuck Scheduler"? That's weird, especially considering how it's not the most convoluted out there. Is there a story behind the name? --94.76.121.220 (talk) 17:39, 24 November 2011 (UTC)

Never mind. I just had to look in the FAQ.

Why "Brain Fuck"?

Because it throws out everything about what we know is good about how to design a modern scheduler in scalability. Because it's so ridiculously simple. Because it performs so ridiculously well on what it's good at despite being that simple. Because it's designed in such a way that mainline would never be interested in adopting it, which is how I like it. Because it will make people sit up and take notice of where the problems are in the current design. Because it throws out the philosophy that one scheduler fits all and shows that you can do a -lot- better with a scheduler designed for a particular purpose. I don't want to use a steamroller to crack nuts. Because it actually means that more CPUs means better latencies. Because I must be fucked in the head to be working on this again. I'll think of some more becauses later.

--94.76.121.220 (talk) 17:42, 24 November 2011 (UTC)

What does it do?[edit]

This article talks about everything EXCEPT how the scheduling algorithm actually schedules.130.209.246.52 (talk) 17:23, 18 March 2014 (UTC)

Good point. That's because there seem to be next to zero published references providing an analysis of the actual BFS' inner workings; in order to have a description of how it actually works, digging through its source code would be required. I could do that, but that would take quite a lot of time, and it would be questionnable whether the BFS' source code could serve as a reference for a description produced that way. — Dsimic (talk | contribs) 03:32, 19 March 2014 (UTC)