From: Peter Zijlstra <peterz@infradead.org>
To: Darren Hart <dvhltc@us.ibm.com>
Cc: Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC][PATCH -rt] sched: fully ignore RT tasks for CFS load-balancing
Date: Wed, 26 Aug 2009 21:04:45 +0200 [thread overview]
Message-ID: <1251313485.18584.33.camel@twins> (raw)
In-Reply-To: <4A958480.3070207@us.ibm.com>
On Wed, 2009-08-26 at 11:52 -0700, Darren Hart wrote:
> Peter Zijlstra wrote:
> > Since -rt runs IRQs and SoftIRQs as RT tasks and load-balancing is done
> > from softirq context, there is always at least one RT task (and very
> > likely multiple) running when we balance.
> >
> > The current (and totally broken) interaction between RT tasks and CFS
> > load-balancing makes it so that we'll try to evacuate a significant
> > amount of tasks due to RT tasks being runnable.
> >
> > Solve this in another broken way by not accounting RT tasks at all.
> >
> > This will likely break another class of cases, but until we can properly
> > fix this, we might as well do this.
>
> Peter,
>
> Do we know why this became a problem lately? I don't recall seeing load
> balancing issues like this way back around 2.6.21 or 22 when CFS was
> released. Is the cpu_load stuff fairly recent?
The earlier problem solved by the previous patch was caused by tglx
tinkering with the cpu_load computation.
This particular problem I'm not sure about, afaict it should have been
present a long long time.
prev parent reply other threads:[~2009-08-26 19:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-26 14:44 [RFC][PATCH -rt] sched: fully ignore RT tasks for CFS load-balancing Peter Zijlstra
2009-08-26 18:52 ` Darren Hart
2009-08-26 19:04 ` 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=1251313485.18584.33.camel@twins \
--to=peterz@infradead.org \
--cc=dvhltc@us.ibm.com \
--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 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.