[lkml]   [2012]   [Mar]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [ANNOUNCE] LinSched for v3.3-rc7

* Paul Turner <> wrote:

> That said, I'm relatively happy with the current state of
> integration, there's certainly some specific areas that can
> still be greatly improved (in particular, the main simulator
> loop has not had as much attention paid as the
> LinSched<>Kernel interactions and there's a long list of TODOs
> that could be improved there), but things are now mated fairly
> cleanly through the use of a new LinSched architecture. This
> is a total re-write of almost all LinSched<>Kernel
> interactions versus the previous (2.6.35) version, and has
> allowed us to now carry almost zero modifications against the
> kernel source. It's both possible to develop/test in place,
> as well as being patch compatible. The remaining touch-points
> now total just 20 lines! Half of these are likely mergable,
> with the other 10 lines being more LinSched specific at this
> point in time, I've broken these down below:
> The total damage:
> include/linux/init.h | 6 ++++++ (linsched ugliness,
> unfortunately necessary until we boot-strap proper initcall support)
> include/linux/rcupdate.h | 3 +++ (only necessary to allow -O0
> compilation which is extremely handy for analyzing the scheduler using
> gdb)
> kernel/pid.c | 4 ++++ (linsched ugliness,
> these can go eventually)
> kernel/sched/fair.c | 2 +- (this is just the
> promotion of 1 structure and function from static state which weren't
> published in the sched/ re-factoring that we need from within the
> simulator)
> kernel/sched/stats.c | 2 +-
> kernel/time/timekeeping.c | 3 ++- (this fixes a time-dilation
> error due to rounding when our clock-source has ns-resolution, e.g.
> shift==1)
> 6 files changed, 17 insertions(+), 3 deletions(-)

Mind sending these preparatory changes as a standalone series as
well, against the upstream scheduler, straight away?

Maybe we can find ways to remove the uglies while reviewing and
integrating all that. Having those bits upstream would make the
rest of linsched a lot easier to merge as well.



 \ /
  Last update: 2012-03-15 08:25    [W:0.125 / U:4.068 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site