Talk:Brain Fuck Scheduler

Unnamed section
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
"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?
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. &mdash; Dsimic (talk | contribs) 03:32, 19 March 2014 (UTC)

External links modified
Hello fellow Wikipedians,

I have just added archive links to 1 one external link on Brain Fuck Scheduler. Please take a moment to review my edit. If necessary, add after the link to keep me from modifying it. Alternatively, you can add to keep me off the page altogether. I made the following changes:
 * Added archive https://web.archive.org/20090922234416/http://android.git.kernel.org:80/?p=kernel/experimental.git;a=shortlog;h=refs/heads/android-2.6.29-bfs to http://android.git.kernel.org/?p=kernel/experimental.git;a=shortlog;h=refs/heads/android-2.6.29-bfs

When you have finished reviewing my changes, please set the checked parameter below to true to let others know.

Cheers.—cyberbot II  Talk to my owner :Online 06:10, 29 January 2016 (UTC)


 * ✅, all fine. &mdash; Dsimic (talk &#124; contribs) 06:57, 29 January 2016 (UTC)

"veteran kernel programmer"
Is "veteran kernel programmer" appropriate on wikipedia?

MuQSS
BFS has been retired by CK in favour of a new scheduler, MuQSS. I'm updating the page to provisionally reflect this fact, should a new article be put together on MuQSS or should there be a discussion on maybe having a single article for both? (Reference: https://ck-hack.blogspot.co.uk/2016/10/linux-48-ck2-muqss-version-0114.html) Argymeg (talk) 12:45, 10 November 2016 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 2 external links on Brain Fuck Scheduler. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20131023055842/http://www.zenwalk.org/modules/news/article.php?storyid=107 to http://www.zenwalk.org/modules/news/article.php?storyid=107
 * Corrected formatting/usage for http://android.git.kernel.org/?p=kernel%2Fexperimental.git%3Ba%3Dshortlog%3Bh%3Drefs%2Fheads%2Fandroid-2.6.29-bfs

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 14:47, 24 July 2017 (UTC)