11-18-2010, 01:44 PM
Placebo, unless you open all those apps from a terminal, AND have a task running that tries to eat up all your resources. Why do people think this patch is some kinda magical thing ?
Originally Posted by kernelOfTruth
Which of the apps you're opening are attached to TTYs ?
I recommend actually reading the thread discussing this patch before you go around calling my prev. post BS.
11-18-2010, 02:54 PM
11-18-2010, 04:52 PM
I don't know if anybody has seen this but its an alternative to the 200 line patch that does the same thing. Just add 4 lines to your bashrc and do two commands on the command line.
benchmarks of both methods
11-18-2010, 04:56 PM
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.
Originally Posted by misGnomer
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.
11-18-2010, 04:59 PM
Thank you for the patch. It applied cleanly and I'm compiling now.
Originally Posted by glasen
11-18-2010, 05:00 PM
Exactly. I posted the same 2 pages back.
Originally Posted by Obscene_CNN
When you translate a 6 line script to a 200 line kernel patch, it suddenly doesn't seem exciting anymore does it.
11-18-2010, 05:15 PM
Just a thought,
Is there a way to use this patch to give an app that runs in a TTY priority over the GUI? In some cases people do have mission critical apps.
11-19-2010, 04:11 AM
Thanks for summarizing it Marco.
Originally Posted by marco
I totally agree with the systemd solution and I am looking forward to testing it. Hopefully this will be availible in package updates for RHEL6(?).
It would be interesting if we could set a approximate date on the history bullets?
11-19-2010, 05:28 AM
can someone backport this patch to the lucid kernel 2.6.32-22 ?
11-20-2010, 02:25 AM
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).
Tags for this Thread