Ultimately the kernel is there to accommodate different user-space cases, with sane defaults, options and all.
The two sides of the whole (i.e us all) need to cooperate; and they do.
Here (the optional) systemd represents users-space tools for adjusting system/kernel behaviour "on-the-fly" and with higher level of granularity.
Still, the ability to configure kernel-space behaviour (at the time of compilation and without specific user-space tools) will be expected.
All the eyeballs are there so... bring on 2011! (the year when Linux... servers take over the desktop!)
This patch is really not supposed to be there! Lennart gave a 6 line script that does exactly the same and Linus said Mike developed the patch the same way.
Linus' concern is that this behaviour is not default, but it should not be default if it is just a policy. I think that's the whole point those guys are arguing about. I do not think this patch is appropriate personally. Go with BFS. BFS rules.
This is a very stupid thread. You could do this with cgroups long ago (for cpu, disk and memory as well). All you need to do is to create wrappers for your favorite (or hated) programs to isolate their resource usage behavior. Read up on this:
And yes, some people here are right. This is not going to magically speed up your program loads or make gcc compile your source faster (if at all, it will be a slow down in throughput: Ingo says its around 5% overhead).