From: Miao Xie <miaox@cn.fujitsu.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Ingo Molnar <mingo@elte.hu>, Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [BUG] sched: fair group's bug
Date: Mon, 23 Feb 2009 19:09:06 +0800 [thread overview]
Message-ID: <49A283D2.8060300@cn.fujitsu.com> (raw)
In-Reply-To: <1231424195.11687.449.camel@twins>
on 2009-1-8 22:16 Peter Zijlstra wrote:
> On Thu, 2009-01-08 at 09:30 +0800, Miao Xie wrote:
>> I tested fair group scheduler on my hyper-threading x86_64 box(2 CPU * 2 HT)
>> and found the deviation of the groups' CPU usage was larger than 2.6.26
>> when *offline* a CPU or do hotplug frequently. It is less than 1% On 2.6.26，but
>> On current kernel, it is often greater than 4%, even than 10% by accident.
>
> Its not a bug -- a scheduler without smp awareness cannot be compared to
> one without -- .26 just wasn't a complete group scheduler.
>
> At best its a regression for your particular workload.
>
Hi, Peter
Do you wait to fix this regression?
Thanks!
Miao
next prev parent reply other threads:[~2009-02-23 11:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 1:30 [BUG] sched: fair group's bug Miao Xie
2009-01-08 3:35 ` Miao Xie
2009-01-08 14:16 ` Peter Zijlstra
2009-02-23 11:09 ` Miao Xie [this message]
2009-01-09 2:45 ` Miao Xie
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=49A283D2.8060300@cn.fujitsu.com \
--to=miaox@cn.fujitsu.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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