The desktop- and interactivity-oriented kernel patches contributed by Con Kolivas are back at kernel.org. Starting on 2.6.32, -ck patches include BFS (aka the Brain Fuck Scheduler) and a few other contributions. Reproducible: Sometimes Steps to Reproduce: Visit http://www.kernel.org/pub/linux/kernel/people/ck/patches/2.6/2.6.32/2.6.32-ck1/patches/ and download patches individually, or get them all at once at http://www.kernel.org/pub/linux/kernel/people/ck/patches/2.6/2.6.32/2.6.32-ck1/ Apply patches to vanilla-sources and get (allegedly) significantly better desktop performance. Actual Results: I tried BFS with vanilla-sources-2.6.30 and it worked fine. Haven't tried the new complete patchset, though. Expected Results: Should be as good as -ck was on the 2.4 kernel series.
I'm using 2.6.32-ck1 on my laptop and my desktop and they actually DO feel a lot more responsive than with gentoo-sources-2.6.32. Sorry, can't contribute an ebuild though, because ebuild building -- especially the kernel ones -- are too complicated for my skills nowadays. I tried using the proposed ebuild for ck-sources-2.6.22-ck1 (bug #184736) but didn't get too far.
Oh wow, this is good news! -ck was my favorite patchset.
-ck2 is out already, and it includes BFS v0.313. Check it out at http://www.kernel.org/pub/linux/kernel/people/ck/patches/2.6/2.6.32/2.6.32-ck2/
Created attachment 215456 [details] Draft (but still non-working) ebuild This ebuild is mostly the same as http://bugs.gentoo.org/attachment.cgi?id=124696 (from bug #184736: "sys-kernel/ck-sources-2.6.22-ck1 version bump"). The problem happens when it tries to "cd ${S}", which points to: /var/tmp/portage/sys-kernel/ck-sources-2.6.32_p2/work/linux-2.6.32_p2 However, the package creates this folder as: /var/tmp/portage/portage/sys-kernel/ck-sources-2.6.32_p2/work/linux-2.6.32-ck2 Feel free to point to a solution.
(In reply to comment #4) > The problem happens when it tries to "cd ${S}", which points to: > /var/tmp/portage/sys-kernel/ck-sources-2.6.32_p2/work/linux-2.6.32_p2 > > However, the package creates this folder as: /var/tmp/portage/sys-kernel/ck-sources-2.6.32_p2/work/linux-2.6.32-ck2 Little mistake on this last line. This is what I meant.
ebuild doesn't work >>> Unpacking genpatches-2.6.32-2.base.tar.bz2 to /var/tmp/portage/sys-kernel/ck-sources-2.6.32_p2/work/patches/000001 * Applying 1000_linux-2.6.32.1.patch (-p0+) ... [ !! ] * Please attach /var/tmp/portage/sys-kernel/ck-sources-2.6.32_p2/temp/1000_linux-2.6.32.1.err to any bug you may post. * ERROR: sys-kernel/ck-sources-2.6.32_p2 failed: * Unable to dry-run patch. *
Created attachment 221459 [details] sys-kernel/ck-sources-2.6.32_p2 ck-sources-2.6.32_p2 ebuild
Created attachment 221461 [details] sys-kernel/ck-sources-2.6.32_p2 ck-sources-2.6.32_p2 (removed some obsolete comments)
Created attachment 221463 [details] sys-kernel/ck-sources-2.6.33_p1 ck-sources-2.6.33_p1
I'm willing to adopt this package.
ck-sources 2.6.32 and 2.6.33 added.
You're missing something, I think. Unless this kernel really is supported by the Security team, you need to stick this in your ebuilds: K_SECURITY_UNSUPPORTED="1" The only officially supported kernel patchsets are gentoo-, hardened-, and ${ARCH}-sources.
Thank you Josh - added to ck-sources, I'll add this variable to tuxonice-sources too :)
Created attachment 241995 [details] 2.6.35 with ck1 and gentoo basic patches.
