tag:blogger.com,1999:blog-6469704299235308349.post7626090612235910862..comments2024-02-09T16:24:46.087+11:00Comments on -ck hacking: 3.2-ck1ckhttp://www.blogger.com/profile/02904761195451530213noreply@blogger.comBlogger56125tag:blogger.com,1999:blog-6469704299235308349.post-17193355461970263102014-05-18T00:40:10.426+10:002014-05-18T00:40:10.426+10:00"Does not work with 3.2.57 and .58 kernel. Ye..."Does not work with 3.2.57 and .58 kernel. Yes with 3.2.2." <br /><br />Unfortunately it's true...Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-91690782393921784952014-05-03T17:23:40.687+10:002014-05-03T17:23:40.687+10:00Does not work with 3.2.57 and .58 kernel. Yes with...Does not work with 3.2.57 and .58 kernel. Yes with 3.2.2.<br /><br />SynFlaghttp://hackingthesystem4fun.blogspot.comnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-836920024255781352013-12-28T17:48:39.752+11:002013-12-28T17:48:39.752+11:00Same problem here, any solutions?
CC arch/x8...Same problem here, any solutions?<br /><br />CC arch/x86/kernel/init_task.o<br />/build/buildd/linux-3.2.0/arch/x86/kernel/init_task.c:31:8: error: unknown field 'deadline' specified in initializer<br />/build/buildd/linux-3.2.0/arch/x86/kernel/init_task.c:31:8: error: unknown field 'run_list' specified in initializer<br />/build/buildd/linux-3.2.0/arch/x86/kernel/init_task.c:31:32: error: 'struct task_struct' has no member named 'run_list'<br />/build/buildd/linux-3.2.0/arch/x86/kernel/init_task.c:31:32: error: 'struct task_struct' has no member named 'run_list'<br />/build/buildd/linux-3.2.0/arch/x86/kernel/init_task.c:31:8: error: unknown field 'time_slice' specified in initializer<br />make[4]: *** [arch/x86/kernel/init_task.o] Error 1<br />make[3]: *** [arch/x86/kernel] Error 2<br />make[2]: *** [arch/x86] Error 2<br />make[1]: *** [sub-make] Error 2Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-42881965383217199782012-09-29T03:02:52.701+10:002012-09-29T03:02:52.701+10:00Mursel, I got the same balalayka. Did you find how...Mursel, I got the same balalayka. Did you find how to fix this issue?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-66185499416607280982012-08-10T22:56:23.489+10:002012-08-10T22:56:23.489+10:00I am using Ubuntu 12.04 and so downloaded the defa...I am using Ubuntu 12.04 and so downloaded the default kernel source from repo:<br /><br />apt-get source linux-image$(uname -r)<br /><br />The above, downloads the official kernel of Ubuntu 12.04 which is the 3.2.0-29.46 (this is build on 3.2.24 mainline of kernel.org). <br /><br />So I downloaded the "patch-3.2-ck1" and successfully applied it. Unfortunately after starting the compilation, a little later I get an error and it stops the compilation:<br /><br /> CC arch/x86/kernel/pcspeaker.o<br /> CC arch/x86/kernel/check.o<br /> CC arch/x86/kernel/devicetree.o<br /> LD arch/x86/kernel/built-in.o<br /> AS arch/x86/kernel/head_32.o<br /> CC arch/x86/kernel/head32.o<br /> CC arch/x86/kernel/head.o<br /> CC arch/x86/kernel/init_task.o<br />/home/user/Public/CompilingFolder/linux-stable/arch/x86/kernel/init_task.c:31:8: error: unknown field ‘deadline’ specified in initializer<br />/home/user/Public/CompilingFolder/linux-stable/arch/x86/kernel/init_task.c:31:8: error: unknown field ‘run_list’ specified in initializer<br />/home/user/Public/CompilingFolder/linux-stable/arch/x86/kernel/init_task.c:31:32: error: ‘struct task_struct’ has no member named ‘run_list’<br />/home/user/Public/CompilingFolder/linux-stable/arch/x86/kernel/init_task.c:31:32: error: ‘struct task_struct’ has no member named ‘run_list’<br />/home/user/Public/CompilingFolder/linux-stable/arch/x86/kernel/init_task.c:31:8: error: unknown field ‘time_slice’ specified in initializer<br />make[4]: *** [arch/x86/kernel/init_task.o] Error 1<br />make[3]: *** [arch/x86/kernel] Error 2<br />make[2]: *** [arch/x86] Error 2<br />make[1]: *** [sub-make] Error 2<br />make[1]: Leaving directory `/home/user/Public/CompilingFolder/linux-stable'<br />make: *** [/home/user/Public/CompilingFolder/linux-stable/debian/stamps/stamp-build-optimus] Error 2<br /><br />Any ideas how I can manage to fix it or why it is happening ?Murselnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-39457959457938286602012-03-16T17:22:12.019+11:002012-03-16T17:22:12.019+11:00pulseaudio is just bells and whistles, it's bl...pulseaudio is just bells and whistles, it's bloated, i don't feel the need for it thanks.anonymous cowardnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-88254649113875684972012-03-15T04:25:29.889+11:002012-03-15T04:25:29.889+11:00@ck:
Maybe... I am really boring you with my comme...@ck:<br />Maybe... I am really boring you with my comments/questions? Your replies make me feel like that. If I would not want to get the best experience from my existing system, what I supposed to be your goal, too, I've never had asked.<br /><br />@anonymous coward:<br />Most recent releases of pulseaudio can manage multiple sources of audio like video + skype + system notifications that alsa was never capable of. Maybe... you like to give it a new try!<br />[Manuel Krause]Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-87257674992764462702012-03-14T19:30:21.425+11:002012-03-14T19:30:21.425+11:00pulseaudio sucks :ppulseaudio sucks :panonymous cowardnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-89406547340867663722012-03-14T10:43:08.680+11:002012-03-14T10:43:08.680+11:00Maybe I don't run pulseaudio and just use alsa...Maybe I don't run pulseaudio and just use alsa? Maybe I don't change any priorities?ckhttps://www.blogger.com/profile/02904761195451530213noreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-70533279486773717642012-03-14T09:27:06.877+11:002012-03-14T09:27:06.877+11:00If I set Xorg to SCHED_ISO (like in autoiso.patch)...If I set Xorg to SCHED_ISO (like in autoiso.patch) input is more responsive.<br />[Manuel Krause]Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-39979638824300842952012-03-14T09:15:11.749+11:002012-03-14T09:15:11.749+11:00Short Question: What priority is your pulseaudio r...Short Question: What priority is your pulseaudio running at?! To have better comparisons!<br />[Manuel Krause]Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-87375115020485313312012-03-14T08:32:45.229+11:002012-03-14T08:32:45.229+11:00Of course there is no "advantage" to set...Of course there is no "advantage" to setting Xorg to SCHED_NORMAL since that's... doing nothing. The issue is in YOUR desktop YOU are running pulseaudio and at nice -11. But that is not everyone, and I need a kernel that works best for everyone. If you find the patch helps you, go right ahead, but I will not include that patch by default.ckhttps://www.blogger.com/profile/02904761195451530213noreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-3413468926140752212012-03-14T07:06:15.733+11:002012-03-14T07:06:15.733+11:00@CK:
There's no real advantage if I set Xorg t...@CK:<br />There's no real advantage if I set Xorg to SCHED_NORMAL (unlike in the autoiso.patch) as it affects the input system as well. Or setting pulseaudio to SCHED_ISO or both. Pulseaudio is running @ NICE -11 (default on here). One of both always suffers somehow when CPU/Gfx/IO are under heavy load. I assume I'd need to experiment with the NICE levels to find out what helps more. But that's quite a boring test work ;-)<br />[Manuel Krause]Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-27515860650797701792012-03-14T06:41:33.363+11:002012-03-14T06:41:33.363+11:00Sorry, English isn't mine either.
My system fe...Sorry, English isn't mine either.<br />My system feels like responding better to desktop input and hardware throughput, e.g. playing videos additionally to other actions. So, that's nothing about "My system is faster." it's about "My system interacts faster with me." <br />From my point of view that has more value than any benchmarked numbers. But it's only subjective, and not reproducible from one to another.<br />[Manuel Krause]Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-6458683352097579192012-03-14T02:43:55.484+11:002012-03-14T02:43:55.484+11:00Sorry, English is not my main language. When you s...Sorry, English is not my main language. When you say "add an overall plus" you mean they make your system a bit faster, right? Or slower?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-29345729178147962572012-03-13T14:03:09.505+11:002012-03-13T14:03:09.505+11:00For the git lover. I set up a git repository to tr...For the git lover. I set up a git repository to trace the linux-stable git tree and add some of my favorite patch sets. Of course, bfs/ck patch set is the major party of them. Current, bfs/ck, bfs and phc-intel are patch sets I am tracing in this reposiroty.<br /><br />Branches, there will be a branch to trace each kind of patch, for example, linux-3.2.y-bfs to trace the BFS patch.<br />Tags, once a stable kernel released and the patch apply successfully and build out, a signed tag will be added, such like v3.2.9-ck1 and so on.<br />Test, a kernel build test will be run to test the patch with kernel release before test. I just use the -gc one by myself, so I have no promises all of them runs ok.<br />Merge strategy, when a new stable kernel version bumped, this repository will be sync-up with the upstream repo( linux-stable.git ). -bfs,-bfq and phc-intel branch will be rebased to the new stable tag, after build test, a tag with patch name sub-fix will be signed. -ck branch will be rebased with the new created -bfs tag, after build test then signed the -ck tag. Finally, -gc branch will be rebased with phc-intel, -ck and -bfq branch, build then signed the tag.<br />To use, the git way, clone the repository, checkout the tag you want and build you kernel. Tarball way, visit the download tab, click on the download link of given tarball format with the tag you want.<br /><br />Repository address: https://bitbucket.org/alfredchen/linux-gcAlfred Chenhttps://www.blogger.com/profile/03164306846702841944noreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-16794628467868931492012-03-13T08:00:02.628+11:002012-03-13T08:00:02.628+11:00Good, that I didn't delete the old kernel comp...Good, that I didn't delete the old kernel compilations .oO<br /><br />One or both of the following patches add an overall plus to the personal(!) feeling of a quickly responding desktop on my vintage machine:<br /> 04.mm-drop_swap_cache_aggressively.patch<br /> 06.mm-background_scan.patch<br />with BFS-416 and current bfq and kernel 3.2.9 (openSUSE).<br /><br />So, that's mainly the same setup as posted on 2012-03-03, with reverting from the ck-patch:<br /> 09.mm-decrease_default_dirty_ratio-1.patch<br /> 08.mm-lru_cache_add_lru_tail-2.patch<br /> 07.mm-idleprio_prio-1.patch<br /> 05.mm-kswapd_inherit_prio-1.patch.orig<br /> 02.mm-minimal_swappiness.patch<br /><br />Too poor: This comment only reflects subjective recognitions with my previously posted testing and daily workflows.<br />But maybe there's some usefulness for some people so that you don't abandon all mm related patches.<br /><br />[Manuel Krause]Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-68824171068890605512012-03-11T10:16:27.461+11:002012-03-11T10:16:27.461+11:00We'll see, I'm just recompiling, meet you ...We'll see, I'm just recompiling, meet you next week.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-38202084965964635522012-03-11T09:07:40.279+11:002012-03-11T09:07:40.279+11:00I never recommended anyone use the autoiso patch. ...I never recommended anyone use the autoiso patch. That's why it was never included in any -ck release. The potential for it blocking audio which is even more important than xorg is why I decided against it.ckhttps://www.blogger.com/profile/02904761195451530213noreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-48597838381213606652012-03-11T05:09:24.910+11:002012-03-11T05:09:24.910+11:00O.k., yes, several times now. ;-) I've realize...O.k., yes, several times now. ;-) I've realized that message, finally.<br />Are there any shareable insights on whether the autoiso-xorg.patch from bfs-313 days and or the schedtool approach are of benefit any more? (I'd always compiled it in. And I was used to 'enhance' a blocking application to finish earlier via schedtool -I `pidofproc app` from time to time.)<br /><br />[Manuel Krause]Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-15116248467533345852012-03-08T09:00:41.590+11:002012-03-08T09:00:41.590+11:00Well I did say I was having trouble validating whe...Well I did say I was having trouble validating whether those patches even did what they're supposed to do any more and I expect I will be abandoning them for 3.3-ck1 and just make it BFS only.ckhttps://www.blogger.com/profile/02904761195451530213noreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-24172217935214962212012-03-08T06:38:06.395+11:002012-03-08T06:38:06.395+11:00Thank you very much for your explanations!
But if ...Thank you very much for your explanations!<br />But if I look at my overlapping /dev/shm that sometimes goes from RAM to swap (and maybe kicks other desktop-related things to disk as well) there should'nt be "double brakes" or triple or even...: for disk I/O, swap related I/O (mm-idleprio_prio-1.patch and mm-kswapd_inherit_prio-1.patch.orig as I read them), and some possible BUGs that make shm <-> RAM <-> swap transitions and vice versa so CPU/Bridge intense.<br />I still cannot reflect, why the removal of my previously mentionned patches from complete CK makes such a difference in desktop's responsiveness.<br />This is no critcism of your patchset related work, please read it as another spot to point your next optimization work to.<br />I seem to be the last one running an uptodate kernel with CK on an over 12 years old machine, that seems to reveal kernel bottlenecks more easily. :-(<br /><br />Feel free to contact [Manuel Krause]Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-14966787957421920792012-03-07T09:09:12.993+11:002012-03-07T09:09:12.993+11:00It's not that simple. Your disk I/O may well b...It's not that simple. Your disk I/O may well be the slowest component in your system, but if you do things to increase the I/O it almost always leads to other slowdowns, usually of the perceptible interactivity type. So you may speed up writing a big file but then your desktop may come to a standstill while you wait for it to write that file. That's why I'm forever doing things in -ck that make I/O slower rather than faster.ckhttps://www.blogger.com/profile/02904761195451530213noreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-9973928135782041992012-03-07T08:25:24.181+11:002012-03-07T08:25:24.181+11:00@Anonymous: From 2.6.38 to 3.2.1 there had been ma...@Anonymous: From 2.6.38 to 3.2.1 there had been many major changes, call them improvements. ;-) But that's several releases away now!<br /><br />[ManuelKrause]Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6469704299235308349.post-16503643462672839762012-03-07T08:16:00.718+11:002012-03-07T08:16:00.718+11:00I'm not the'Anonymous' you may have re...I'm not the'Anonymous' you may have replied to, earlier, though.<br /><br />Best regards<br />[Manuel Krause]Anonymousnoreply@blogger.com