All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <srostedt@redhat.com>
To: Gregory Haskins <ghaskins@novell.com>
Cc: Dmitry Adamushko <dmitry.adamushko@gmail.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Ingo Molnar <mingo@elte.hu>, Balbir Singh <balbir@in.ibm.com>,
	vatsa@linux.vnet.ibm.com,
	LKML Kernel <linux-kernel@vger.kernel.org>
Subject: Re: RT Load balance changes in sched-devel
Date: Sun, 09 Dec 2007 19:57:13 -0500	[thread overview]
Message-ID: <475C8EE9.2040608@redhat.com> (raw)
In-Reply-To: <475BEE6B.BA47.005A.0@novell.com>

Gregory Haskins wrote:
>> btw., both cases would be addressed by placing load-balance points
>> into sched_class_rt->{enqueue,dequeue}_task_rt()... push_rt_tasks()
>> and pull_rt_tasks() respectively. As a side effect (I think,
>> technically, it would be possible), 3 out of 4 *_balance_rt() calls
>> (the exception: schedule_tail_balance_rt()) in schedule() would become
>> unnecessary.
>>
>> _BUT_
>>
>> the enqueue/dequeue() interface would become less straightforward,
>> logically-wise.
>> Something like:

Also push and pull_rt use activate,deactivate as well. So this would 
make that code a bit more complex.

>>
>> rq = activate_task(rq, ...) ; /* may unlock rq and lock/return another one 
>> */
>>
>> would complicate the existing use cases.
>>
> 
> I think I would prefer to just fix the setscheduler/setprio cases for the class transition than change the behavior of these enqueue/dequeue calls.  But I will keep an open mind as I look into this issue.

I agree with Gregory on this. I prefer to fix the two you found. I 
thought about them before, but somehow they were missed :-/

Anyway, I'll be working on adding some more patches on Monday. There may 
be other ways to clean this up.

> 
> Thanks for the review!

Yeah, thanks from me too!

-- Steve


  reply	other threads:[~2007-12-10  0:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20071130145939.GN5681@linux.vnet.ibm.com>
     [not found] ` <b647ffbd0712011156p252ae29dnfa75494e4d2c845c@mail.gmail.com>
     [not found]   ` <20071203182223.GA4133@linux.vnet.ibm.com>
     [not found]     ` <47556B23.2060909@redhat.com>
     [not found]       ` <20071204153542.GC3388@linux.vnet.ibm.com>
     [not found]         ` <b647ffbd0712040828l51a26a82jc0f38d3f4aa2291e@mail.gmail.com>
     [not found]           ` <20071205134036.GA21933@linux.vnet.ibm.com>
     [not found]             ` <4756B8E9.3080709@redhat.com>
     [not found]               ` <20071205164800.GA24767@linux.vnet.ibm.com>
     [not found]                 ` <4756D709.1020901@redhat.com>
2007-12-09 17:16                   ` RT Load balance changes in sched-devel Dmitry Adamushko
2007-12-09 18:32                     ` Gregory Haskins
2007-12-10  0:57                       ` Steven Rostedt [this message]
2007-12-10  2:53                       ` [PATCH RFC] sched: Fixed missed rt-balance points on priority shifts Gregory Haskins
2007-12-10  3:18                         ` Gregory Haskins

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=475C8EE9.2040608@redhat.com \
    --to=srostedt@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=balbir@in.ibm.com \
    --cc=dmitry.adamushko@gmail.com \
    --cc=ghaskins@novell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=vatsa@linux.vnet.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.