linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Ankita Garg <ankita@in.ibm.com>
Cc: Gregory Haskins <ghaskins@novell.com>,
	linux-rt-users <linux-rt-users@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>, Steven Rostedt <rostedt@goodmis.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RT] [PATCH] Make scheduler root_domain modular (sched_classspecific)
Date: Sun, 23 Mar 2008 12:53:04 +0100	[thread overview]
Message-ID: <1206273184.6437.106.camel@lappy> (raw)
In-Reply-To: <20080323113738.GB8082@in.ibm.com>

On Sun, 2008-03-23 at 17:07 +0530, Ankita Garg wrote:
> Hi Peter,
> 
> On Sun, Mar 23, 2008 at 12:27:07PM +0100, Peter Zijlstra wrote:
> > On Sun, 2008-03-23 at 14:32 +0530, Ankita Garg wrote:
> > > Hi Gregory,
> > > 
> > > On Sat, Mar 22, 2008 at 12:04:04PM -0600, Gregory Haskins wrote:
> > > > >>> On Sat, Mar 22, 2008 at 10:29 AM, in message
> > > > <20080322142915.GA9478@in.ibm.com>, Ankita Garg <ankita@in.ibm.com> wrote: 
> > > > > Hello,
> > > > > 
> > > > > Thanks Gregory for clarifying my question on root_domains infrastructure. 
> > > > > What
> > > > > I was effectively mentioning on irc the other day was to make the 
> > > > > root_domain
> > > > > infrastructure modular, ie sched_class specific. Currently, only rt is 
> > > > > making
> > > > > use of this infrasture. Making it modular would enable ease of extension to
> > > > > other sched_classes if required. Trivial patch to that effect.
> > > > > 
> > > > > Patch compile and boot tested.
> > > > 
> > > > Hi Ankita,
> > > >   Very nice, thanks!  Couple of minor nits and further cleanup opportunities inline, but otherwise:
> > > >
> > > > Acked-by: Gregory Haskins <ghaskins@novell.com>
> > > > 
> > > > > 
> > > The changes you have suggested are consistent with what we do for rt_rq
> > > and cfs_rq. Here is the patch with these modifications.
> > 
> > As this patch doesn't touch -rt specific code you should have provided a
> > patch against the upstream code in sched-devel/latest.
> >
> 
> The cpupri bits have not been added to the sched-devel tree yet. This
> patch involves linking to the cpupri from the rt_root_domain. Thus  the
> patch against the latest RT tree. Pl let me know if I understand it
> incorrectly.

The root_domain code is upstream and not -rt specific, that -rt carries
a patch that touches this code is perhaps unfortunate.

We strive to keep the -rt patch as small as possible, that means push
stuff upstream whenever possible. As your patch doesn't change anything
specific to -rt, upstream is the right place to restructure the
root_domain code. Next time the -rt tree gets fwd ported the cpupri bits
will be made to match.




      reply	other threads:[~2008-03-23 11:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-22 14:29 [RT] [PATCH] Make scheduler root_domain modular (sched_class specific) Ankita Garg
2008-03-22 18:04 ` [RT] [PATCH] Make scheduler root_domain modular (sched_classspecific) Gregory Haskins
2008-03-23  9:02   ` Ankita Garg
2008-03-23 11:27     ` Peter Zijlstra
2008-03-23 11:37       ` Ankita Garg
2008-03-23 11:53         ` Peter Zijlstra [this message]

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=1206273184.6437.106.camel@lappy \
    --to=a.p.zijlstra@chello.nl \
    --cc=ankita@in.ibm.com \
    --cc=ghaskins@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).