mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Srivatsa Vaddagiri <vatsa@in.ibm.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Mike Galbraith <efault@gmx.de>,
	Arjan van de Ven <arjan@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Balbir Singh <balbir@linux.vnet.ibm.com>,
	Dmitry Adamushko <dmitry.adamushko@gmail.com>
Subject: Re: [patch] CFS scheduler, -v15
Date: Wed, 6 Jun 2007 13:13:17 +0530	[thread overview]
Message-ID: <20070606074317.GB3274@in.ibm.com> (raw)
In-Reply-To: <20070606070143.GA7375@elte.hu>

On Wed, Jun 06, 2007 at 09:01:43AM +0200, Ingo Molnar wrote:
> [...] and my tree already contains the fixes for rt task's 
> exec_start. 

Can I have this snapshot pls? I have to deal with the same issue when 
the current task switches groups and I was planning to fix it by
introducing a set_curr_task() method in fair_sched_class which
initializes exec_start and other fields for that task.

> > Also, real-time tasks are currently influencing fair clock 
> > calculations (because there is only one raw_weighted_load field per 
> > runqueue). Is that intentional?
> 
> yep - the 'fair clock' in essence freezes when RT tasks are running (but 
> not completely). Can you think of any bad effect from this perhaps?

hmm ..i was thinking of the case where currently running task belongs to 
fair_sched class but the raw_weighted_load field of runqueue includes
weight from real time tasks (which would have affected the delta_mine
calculation). Now I realize that it is not possible because real-time
tasks always preempt fair-sched tasks. So possibly this is not an issue.

> It's useful to have unified load-balancing (smpnice-driven) between the RT 
> and fair classes.

Sure ..the unified weight number is usefull to pick the busiest
group/queue during load balance. I am retaining this aspect in my
patches (which I am preparing to send against -v15 atm).

-- 
Regards,
vatsa

  reply	other threads:[~2007-06-06  7:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-31 15:09 Ingo Molnar
2007-06-06  6:42 ` Srivatsa Vaddagiri
2007-06-06  7:01   ` Ingo Molnar
2007-06-06  7:43     ` Srivatsa Vaddagiri [this message]
2007-06-06  9:08       ` Dmitry Adamushko
2007-06-06 10:37         ` Balbir Singh
2007-06-06 10:59           ` Srivatsa Vaddagiri
2007-06-06 11:19             ` Dmitry Adamushko
2007-06-06 11:37               ` Srivatsa Vaddagiri
2007-06-06 11:46                 ` Srivatsa Vaddagiri
2007-06-14 12:43                 ` Srivatsa Vaddagiri

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=20070606074317.GB3274@in.ibm.com \
    --to=vatsa@in.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=dmitry.adamushko@gmail.com \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®