BFS v0.313 CPU scheduler for 2.6.32
in [Kernel]
|
Prev: [tip:x86/asm] x86: Lift restriction on the location of FIX_BTMAP_*
Next: Unprivileged: Disable raising of privileges
From: Con Kolivas on 30 Dec 2009 07:40 A stupid mismerge in __might_sleep meant that with the right config options dmesg would have been swamped with false warnings. This also was making BFS consume a lot of CPU under certain conditions in combination with preempt RCU. Thanks to Jayson R King for picking it up! There are no other changes in this version compared to 312 full patch: http://ck.kolivas.org/patches/bfs/2.6.32-sched-bfs-313.patch incremental: http://ck.kolivas.org/patches/bfs/2.6.32-bfs312-313.patch I highly recommend BFS users upgrade. Regards, -- -ck -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Thomas Backlund on 30 Dec 2009 09:00 Con Kolivas skrev 30.12.2009 14:34: > A stupid mismerge in __might_sleep meant that with the right config > options dmesg would have been swamped with false warnings. This also > was making BFS consume a lot of CPU under certain conditions in > combination with preempt RCU. > > Thanks to Jayson R King for picking it up! > > There are no other changes in this version compared to 312 > > full patch: > http://ck.kolivas.org/patches/bfs/2.6.32-sched-bfs-313.patch > > incremental: > http://ck.kolivas.org/patches/bfs/2.6.32-bfs312-313.patch > > I highly recommend BFS users upgrade. > Nice. any timeline for a version for 2.6.33 series kernels ? -- Thomas -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Con Kolivas on 30 Dec 2009 09:50 2009/12/31 Thomas Backlund <tmb(a)mandriva.org>: > any timeline for a version for 2.6.33 series kernels ? To minimise my workload I won't start syncing up till an end is in sight to the rc kernels I'm sorry to say. That's usually around rc8 these days... Regards, Con -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Miguel Botón on 30 Dec 2009 13:10 On Wed, Dec 30, 2009 at 2:55 PM, Thomas Backlund <tmb(a)mandriva.org> wrote: > Nice. > > any timeline for a version for 2.6.33 series kernels ? If you want to try BFS on a 2.6.33 kernel, you can try this 'unofficial' port: http://git.zen-kernel.org/?p=kernel/zen.git;a=shortlog;h=refs/heads/sched-bfs I'm currently using it with no issues so far. Greetings, -- Miguel Botón -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Heinz Diehl on 30 Dec 2009 15:00
On 30.12.2009, Miguel Bot�n wrote: > If you want to try BFS on a 2.6.33 kernel, you can try this 'unofficial' port: > http://git.zen-kernel.org/?p=kernel/zen.git;a=shortlog;h=refs/heads/sched-bfs > I'm currently using it with no issues so far. Your patch applies cleanly to 2.6.33-rc2, but compilation fails: [....] In file included from kernel/sched.c:2: kernel/sched_bfs.c: In function '__sched_setscheduler': kernel/sched_bfs.c:3484: warning: passing argument 1 of 'spinlock_check' from incompatible pointer type kernel/sched_bfs.c:3493: warning: passing argument 1 of 'spin_unlock_irqrestore' from incompatible pointer type kernel/sched_bfs.c:3509: warning: passing argument 1 of 'spin_unlock_irqrestore' from incompatible pointer type kernel/sched_bfs.c: In function 'sys_sched_yield': kernel/sched_bfs.c:3846: warning: passing argument 1 of '_raw_spin_unlock' from incompatible pointer type kernel/sched_bfs.c: At top level: kernel/sched_bfs.c:6018: error: conflicting types for 'partition_sched_domains' include/linux/sched.h:1025: error: previous declaration of 'partition_sched_domains' was here kernel/sched_bfs.c: In function 'sched_init': kernel/sched_bfs.c:6425: warning: passing argument 2 of 'plist_head_init' from incompatible pointer type kernel/sched_bfs.c: In function 'normalize_rt_tasks': kernel/sched_bfs.c:6499: warning: passing argument 1 of 'spinlock_check' from incompatible pointer type kernel/sched_bfs.c:6513: warning: passing argument 1 of 'spin_unlock_irqrestore' from incompatible pointer type make[1]: *** [kernel/sched.o] Error 1 make[1]: *** Waiting for unfinished jobs.... CC arch/x86/kernel/alternative.o CC fs/open.o [....] [....] CC arch/x86/kernel/init_task.o LDS arch/x86/kernel/vmlinux.lds CC [M] arch/x86/kernel/msr.o CC [M] arch/x86/kernel/cpuid.o CC [M] arch/x86/kernel/microcode_core.o CC [M] arch/x86/kernel/microcode_amd.o arch/x86/kernel/init_task.c:31: warning: missing braces around initializer arch/x86/kernel/init_task.c:31: warning: (near initialization for 'init_task.pi_lock') arch/x86/kernel/init_task.c:31: error: incompatible types in initialization arch/x86/kernel/init_task.c:31: error: initializer element is not constant arch/x86/kernel/init_task.c:31: error: (near initialization for 'init_task.dirties.lock') arch/x86/kernel/init_task.c:31: error: initializer element is not constant arch/x86/kernel/init_task.c:31: error: (near initialization for 'init_task.perf_event_mutex.wait_lock') make[2]: *** [arch/x86/kernel/init_task.o] Error 1 make[2]: *** Waiting for unfinished jobs.... make[1]: *** [arch/x86/kernel] Error 2 make: *** [arch/x86] Error 2 liesel:/usr/src/linux-2.6.33-rc2 # -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |