From: Peter Zijlstra <peterz@infradead.org>
To: Mike Galbraith <efault@gmx.de>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: commit e9e9250b: sync wakeup bustage when waker is an RT task
Date: Mon, 17 May 2010 10:52:25 +0200 [thread overview]
Message-ID: <1274086345.5605.3727.camel@twins> (raw)
In-Reply-To: <1274086140.5605.3719.camel@twins>
On Mon, 2010-05-17 at 10:49 +0200, Peter Zijlstra wrote:
> On Mon, 2010-05-17 at 06:38 +0200, Mike Galbraith wrote:
> > What would be the harm/consequence of restoring RT tasks to rq->load so
> > the wake_affine()::sync logic just worked as before without hackery?
>
> Well, you'd have to constantly adjust the task weight of RT tasks to
> reflect their actual consumption. Not really feasible.
>
> So the proportional stuff works like:
>
> slice_i = w_i / (\Sum_j w_j) * dt
>
> Giving a RT task a sensible weight we'd have to reverse that:
>
> w_i = slice_i/dt * (\Sum_j w_j)
Another point to note is that this requires we track per-RT-task usage
averages, whereas the cpu_power approach simply lumps everything !fair
(one of the things still on the TODO list is account for IRQ overhead)
into a single large bucket and doesn't care.
next prev parent reply other threads:[~2010-05-17 8:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-15 11:57 commit e9e9250b: sync wakeup bustage when waker is an RT task Mike Galbraith
2010-05-15 12:04 ` Peter Zijlstra
2010-05-15 17:07 ` Mike Galbraith
2010-05-15 17:32 ` Mike Galbraith
2010-05-16 7:21 ` Mike Galbraith
2010-05-17 4:38 ` Mike Galbraith
2010-05-17 8:49 ` Peter Zijlstra
2010-05-17 8:52 ` Peter Zijlstra [this message]
2010-05-17 9:04 ` Mike Galbraith
2010-05-31 11:56 ` Peter Zijlstra
2010-05-31 13:56 ` Mike Galbraith
2010-05-31 14:28 ` Peter Zijlstra
2010-05-31 18:03 ` Mike Galbraith
2010-06-01 6:40 ` Mike Galbraith
2010-06-01 9:12 ` [tip:sched/urgent] sched: Fix wake_affine() vs RT tasks tip-bot for Peter Zijlstra
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=1274086345.5605.3727.camel@twins \
--to=peterz@infradead.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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