You are not logged in.
crocowhile wrote:aha. no, I am still alive. The kernel is compiled but I didn't have time to start it up and compare yet. A small baby with a stomach bug is incompatible with any form of kernel hacking. Also, the computer I have at home is old; at work I have a i7 and I better try that one anyway.
Sorry to hear abt the baby, but...you're not going to keep us waiting till tomorrow, are you?? Got a PKGBUILD to share?
Just use the one in the archwiki: https://wiki.archlinux.org/index.php/Ke … rom_Source and change the version numbers.
Didn't have time to try it yet but I see few people reported nice results. Cool.
Offline
packages are here http://pkgbuild.com/~ioni/
i didn't bump pkgrel at all so keep that in mind when the next kernel upgrade occurs in the repo
Give what you have. To someone, it may be better than you dare to think.
Offline
@wonder - thank You very much for the packages.
I will test a bit more, don't want to have any false hopes, but right now I am running 64bit patched kernel on a system with newest packages from testing, under KDE 4.5 and it is either placebo or there really is a difference. Earlier, when I was starting desktop environment, dropbox began to mangle the data and I tried to start almost anything - the "lag" was noticeable. Right now I started kde, then dropbox, eclipse, emacs, dolphin in a 400GB folder with lots & lots of small media files and I was able to smoothly scroll reddit.com in chromium.
Bravo.
Last edited by praavDa (2010-11-17 17:09:46)
gvim -c "exec \"normal itYNQ#v'Z#ABG#GUR#BAYL#BAR\"|%s/#/ /g|normal ggVGg?ggVG~"
Offline
Just use the one in the archwiki: https://wiki.archlinux.org/index.php/Ke … rom_Source and change the version numbers.
Didn't have time to try it yet but I see few people reported nice results. Cool.
Thanks, I went the kernel26-bzr route. Just wasn't sure where you got the patch from and to which kernel version you applied it to.
Just curious if anybody who used -ck patches compared them to this one? From my own experience, BFS scheduler didn't change my system responsiveness a slightest bit, prolly difference is more visible on older hardware.
Last edited by Jurassic (2010-11-17 17:33:09)
Arch linux
Offline
packages are here http://pkgbuild.com/~ioni/
i didn't bump pkgrel at all so keep that in mind when the next kernel upgrade occurs in the repo
Thanks for the link! How do I test this? Just install with pacman -U and it's done?
Offline
@KlavKalashj and reboot
Give what you have. To someone, it may be better than you dare to think.
Offline
What exacly does this patch do (besides wonders)? Does it patch up CFS or what (in which case it's incopatible with BFS?).
And why is it "designed to automatically create task groups per TTY in an effort to improve the desktop interactivity"? Does that mean I must run each task in a seperate TTY? What's going on if I would run them from Openbox menu as I usually do?
Last edited by karabaja4 (2010-11-17 18:55:42)
Offline
The 2.6.36 patch from the Russian site mentioned earlier works very well, noticeably more responsive. I did the patching myself, not using the packages provided by "wonder".
Anyway, to test aside from running glxgears, browsing, and seeing the general responsiveness improve, do the following to check the kernel:
sysctl -A | grep autogroup
Response should be:
kernel.sched_autogroup_enabled = 1
--
JSkier
Offline
What exacly does this patch do (besides wonders)? Does it patch up CFS or what (in which case it's incopatible with BFS?).
And why is it "designed to automatically create task groups per TTY in an effort to improve the desktop interactivity"? Does that mean I must run each task in a seperate TTY? What's going on if I would run them from Openbox menu as I usually do?
From the config entry:
+ help
+ This option optimizes the scheduler for common desktop workloads by
+ automatically creating and populating task groups. This separation
+ of workloads isolates aggressive CPU burners (like build jobs) from
+ desktop applications. Task group autogeneration is currently based
+ upon task tty association.
It patches the complete fair scheduler, so you have to use CFS and not BFS, thus the "incompatibility" with BFS.
Offline
From the config entry:
/* cut */
It patches the complete fair scheduler, so you have to use CFS and not BFS, thus the "incompatibility" with BFS.
Ok, I kinda assumed that one. But what about my second question? If I were to use improvements that this patch offers, I must run each heavy task in it's own seperate tty? What if I run multiple tasks simultaneously from an Openbox menu or from a file manager?
.
Last edited by karabaja4 (2010-11-17 19:39:13)
Offline
There's actually a nice discussion going on the kernel mailing list. The patch is only usefull if you do tasks that have a tty attached to it. If you only use typical desktop apps, it won't help alot:
http://lkml.indiana.edu/hypermail/linux … 00301.html
http://lkml.indiana.edu/hypermail/linux … 00331.html
Offline
Found an interesting article:
Offline
Well, then I guess my assumption about scheduler shuffling processes between available tty's (reassigning cgroups) depending on load was wrong?
How does it work in phoronix tests then? I didn't see 'em dropping to another tty to start kbuild. I'm confused
Arch linux
Offline
What SCHED_AUTOGROUP does is it automatically configures a rarely used Linux feature (cgroups) to group together related processes so that, under heavy load, certain processes still remain performant under the kernel scheduler.
Offline
After reading the mailing lists, it seems that it effects processes that use a terminal. This is serious business if you are compiling stuff.
http://lkml.org/lkml/2010/11/16/426
Last edited by slytux (2010-11-17 23:24:09)
Offline
Well, then I guess my assumption about scheduler shuffling processes between available tty's (reassigning cgroups) depending on load was wrong?
How does it work in phoronix tests then? I didn't see 'em dropping to another tty to start kbuild. I'm confused
What SCHED_AUTOGROUP does is it automatically configures a rarely used Linux feature (cgroups) to group together related processes so that, under heavy load, certain processes still remain performant under the kernel scheduler.
I guess this post in kernel mailing list should explain it all. It looks like it does infact involve different ttys:
http://lkml.indiana.edu/hypermail/linux … 00428.html
After reading, the mailing lists, it seems that it effects processes that use a terminal. This is serious business if you are compiling stuff.
Perhaps. But still, I don't do lot of -jXY compiling myself. They made a huge fuss about this, because most of developers spend alot of time compiling their stuff (including Linus, which was very happy with this patch for that reason). I'll just stick to BFS.
Last edited by karabaja4 (2010-11-17 20:33:28)
Offline
I guess this post in kernel mailing list should explain it all. It looks like it does infact involve different ttys:
No, it doesn't explain how phoronix guys were able to see such a drastic difference w/o starting make -j32 in a separate tty
Arch linux
Offline
Linus had some words for Mr. Lennart
http://lkml.indiana.edu/hypermail/linux … 00300.html
http://lkml.indiana.edu/hypermail/linux … 00419.html
Offline
Don't forget that your terminal emulator gets allocated a pseudo tty. To find out what the controlling TTY for your shell is called, run ps l or you could simply run the tty command.
Last edited by slytux (2010-11-17 20:43:00)
Offline
packages are here http://pkgbuild.com/~ioni/
i didn't bump pkgrel at all so keep that in mind when the next kernel upgrade occurs in the repo
uhuh thanks Wonder , very appreciated!
Offline
No, it doesn't explain how phoronix guys were able to see such a drastic difference w/o starting make -j32 in a separate tty
Don't forget that your terminal emulator gets allocated a pseudo tty.
That would mean that phoronix guys ran all these apps on the desktop from different pseudo-ttys, and that pseudo-ttys are affected by this patch just like "real" ttys? *looking at the bunch*
@Linus vs. Lennart on ML: man, those are some harsh words...
.
Last edited by karabaja4 (2010-11-17 20:53:00)
Offline
Would this also mean that you get to enjoy the patch benefits ONLY if you start applications from separate x-terminals and not from the menu?
Arch linux
Offline
Anything not launched from a virtual terminal or a terminal emulator won't get autogrouped into a cgroup, so this patch ignores normal desktop applications. That just means they get treated as interactive though (and the terminal apps are prevented from slowing them down).
This patch ONLY helps you if you do stuff in the terminal that used to cause desktop lag.
Last edited by thestinger (2010-11-17 21:01:52)
Offline
Would this also mean that you get to enjoy the patch benefits ONLY if you start applications from separate x-terminals and not from the menu?
I guess so, yeah I was saying above, they made too big a fuss about this because this is only important to people that do alot of compiling. Here, I just found a more detailed explanation:
Offline
Would this also mean that you get to enjoy the patch benefits ONLY if you start applications from separate x-terminals and not from the menu?
well , yes...
The only problem is that *desktop* users use *desktop* apps, which
never have a controlling tty.This is a *nerd* config not helping any regular desktop user. You guys
are optimizing the system for people who build kernels and watch
movies at the same time, not for desktop users. Hooking into TTYs
works for almost nobody sane out there.It's all fine, no comment on the patch, it's a nice hack. But please
stop talking about the *desktop* here, it has almost nothing to do
with it.
but we're all nerd here, no?
Offline