All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Paul Turner <pjt@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Paul McKenney <paulmck@linux.vnet.ibm.com>,
	Benjamin Segall <bsegall@google.com>,
	Ranjit Manomohan <ranjitm@google.com>,
	Nikhil Rao <ncrao@google.com>,
	jmc@cs.unc.edu, Dhaval Giani <dhaval.giani@gmail.com>,
	Suresh Siddha <suresh.b.siddha@intel.com>,
	Srivatsa Vaddagiri <vatsa@in.ibm.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] LinSched for v3.3-rc7
Date: Thu, 15 Mar 2012 08:21:24 +0100	[thread overview]
Message-ID: <20120315072124.GA29161@elte.hu> (raw)
In-Reply-To: <CAPM31RL6Sk6cNR9MzW_7XDvfkMA1q6xK_mcJJaCMY8Ex___9+A@mail.gmail.com>


* Paul Turner <pjt@google.com> 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.

Thanks,

	Ingo

  parent reply	other threads:[~2012-03-15  7:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-15  3:58 [ANNOUNCE] LinSched for v3.3-rc7 Paul Turner
2012-03-15  4:08 ` Dhaval Giani
2012-03-21  9:20   ` Michael Wang
2012-03-21  9:54     ` Paul Turner
2012-03-21 10:11       ` Michael Wang
2012-03-21 14:20   ` Morten Rasmussen
2012-03-15  7:21 ` Ingo Molnar [this message]
2012-03-23  4:03 ` Michael Wang
2012-03-28  5:19   ` Michael Wang
2012-04-09  3:29 ` Michael Wang
2012-07-23  3:03 ` Michael Wang
2012-07-23 12:54   ` Paul Turner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120315072124.GA29161@elte.hu \
    --to=mingo@elte.hu \
    --cc=bsegall@google.com \
    --cc=dhaval.giani@gmail.com \
    --cc=jmc@cs.unc.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ncrao@google.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=pjt@google.com \
    --cc=ranjitm@google.com \
    --cc=suresh.b.siddha@intel.com \
    --cc=vatsa@in.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.