> -----Message d'origine----- > De : [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] De la part de Ingo Molnar > > By popular demand, here is release -v24 of the CFS scheduler patch. > > It is a full backport of the latest & greatest scheduler code > to v2.6.24-rc3, v2.6.23.8, v2.6.22.13, v2.6.21.7. The patches > can be downloaded from the usual place: > > http://people.redhat.com/mingo/cfs-scheduler/ > > There's tons of changes since v22 was released: > > 36 files changed, 2359 insertions(+), 1082 deletions(-) > > that's 187 individual commits from 32 authors. > > So even if CFS v22 worked well for you, please try this > release too and report regressions (if any). >
Hi Ingo, Thnx a lot for theses backports... Ran into this while compiling a 2.6.22.13 with CFS v24 CC kernel/sched.o kernel/sched.c: In function 'cpu_to_core_group': kernel/sched.c:6056: error: 'per_cpu__cpu_sibling_map' undeclared (first use in this function) kernel/sched.c:6056: error: (Each undeclared identifier is reported only once kernel/sched.c:6056: error: for each function it appears in.) kernel/sched.c:6056: warning: type defaults to 'int' in declaration of 'type name' kernel/sched.c:6056: error: invalid type argument of 'unary *' kernel/sched.c: In function 'build_sched_domains': kernel/sched.c:6319: error: 'per_cpu__cpu_sibling_map' undeclared (first use in this function) kernel/sched.c:6319: warning: type defaults to 'int' in declaration of 'type name' kernel/sched.c:6319: error: invalid type argument of 'unary *' kernel/sched.c:6330: warning: type defaults to 'int' in declaration of 'type name' kernel/sched.c:6330: error: invalid type argument of 'unary *' make[2]: *** [kernel/sched.o] Error 1 make[1]: *** [kernel] Error 2 make[1]: Leaving directory `/usr/src/linux-headers-2.6.22.13-cfs-sarge-686-envcan' make: *** [debian/stamp-build-kernel] Error 2 - vin - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
