2.6.37-ck1

2.6.37-ck1

[Con Kolivas]

These are patches designed to improve system responsiveness and interactivity 
with specific emphasis on the desktop, but suitable to any workload.


Apply to 2.6.37:
http://www.kernel.org/pub/linux/kernel/people/ck/patches/2.6/2.6.37/2.6.37-
ck1/patch-2.6.37-ck1.bz2

Broken out tarball:
http://www.kernel.org/pub/linux/kernel/people/ck/patches/2.6/2.6.37/2.6.37-
ck1/2.6.37-ck1-broken-out.tar.bz2

Discrete patches:
http://www.kernel.org/pub/linux/kernel/people/ck/patches/2.6/2.6.37/2.6.37-
ck1/patches/

All -ck patches:
http://www.kernel.org/pub/linux/kernel/people/ck/patches/


Web:
http://kernel.kolivas.org

Code blog when I feel like it:
http://ck-hack.blogspot.com/

Each discrete patch contains a brief description of what it does at the top of 
the patch itself.


The most significant change is an updated BFS CPU scheduler, up to version 
0.363. See the announce of that patch for the changelog. The rest is a resync.


2.6.37-sched-bfs-363.patch
sched-add-above-background-load-function.patch
mm-make_swappiness_really_mean_it.patch
mm-zero_swappiness.patch
mm-enable_swaptoken_only_when_swap_full.patch
mm-drop_swap_cache_aggressively.patch
mm-kswapd_inherit_prio-1.patch
mm-background_scan.patch
mm-idleprio_prio-1.patch
mm-lru_cache_add_lru_tail.patch
mm-decrease_default_dirty_ratio.patch
kconfig-expose_vmsplit_option.patch
hz-default_1000.patch
hz-no_default_250.patch
hz-raise_max.patch
preempt-desktop-tune.patch
cpufreq-bfs_tweaks.patch
ck1-version.patch



I'll be offline shortly and in Japan for a few weeks so I'll be unlikely to 
respond to any emails in that time.

Enjoy!
Con
-- 
-ck

Re: 2.6.37-ck1

[walt]

On 01/05/2011 09:19 PM, Con Kolivas wrote:
> These are patches designed to improve system responsiveness and interactivity
> with specific emphasis on the desktop, but suitable to any workload.
>
>
> Apply to 2.6.37:
> http://www.kernel.org/pub/linux/kernel/people/ck/patches/2.6/2.6.37/2.6.37-
> ck1/patch-2.6.37-ck1.bz2

Thanks Con.  I can't build a ck kernel without CONFIG_HOTPLUG_CPU but I don't
know if this is a bug or a feature :)

Your latest sched_bfs.c encloses the subroutine sched_set_stop_task() inside of
an #ifdef CONFIG_HOTPLUG_CPU section.

But the most recent stop_machine.c uses that subroutine twice -- once inside of
an #ifdef CONFIG_HOTPLUG_CPU section, and again outside of that section.

The result is that stop_machine.o still needs sched_set_stop_task() even if
CONFIG_HOTPLUG_CPU is not defined, so the build fails in the link stage with
a missing symbol error.

Thanks for any suggestions/clarifications.