From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: vatsa@linux.vnet.ibm.com
Cc: Mike Galbraith <efault@gmx.de>,
"Zhang, Yanmin" <yanmin_zhang@linux.intel.com>,
Dhaval Giani <dhaval@linux.vnet.ibm.com>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Aneesh Kumar KV <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: volanoMark regression with kernel 2.6.26-rc1
Date: Wed, 14 May 2008 17:12:47 +0200 [thread overview]
Message-ID: <1210777967.10126.17.camel@twins> (raw)
In-Reply-To: <20080514134414.GA12693@linux.vnet.ibm.com>
> +#define GROUP_SCALE (2*1024)
> +
> static inline void inc_cpu_load(struct rq *rq, unsigned long load)
> {
> + load *= GROUP_SCALE;
> update_load_add(&rq->load, load);
> }
>
> static inline void dec_cpu_load(struct rq *rq, unsigned long load)
> {
> + load *= GROUP_SCALE;
> update_load_sub(&rq->load, load);
> }
Yeah, this bit makes a huge difference; I do that by:
mkdir /cgroup/foo
for i in `cat /cgroup/tasks`; do echo $i > /cgroup/foo/tasks; done
echo $((1024*1024)) > /cgroup/foo/cpu.shares
I'm still pulling my hairs out on why this makes a difference though - I
eliminated all direct assumption on SCHED_LOAD_SCALE(_FUZZ) with an
average of the weight per task. - but all that doesn't help (much)
A few other things I found that make a significant difference:
+static void update_aggregate(int cpu, struct sched_domain *sd)
+{
+ aggregate_walk_tree(aggregate_get_down, aggregate_get_nop, cpu, sd);
+}
@@ -3224,6 +3189,8 @@ static int move_tasks(struct rq *this_rq, int this_cpu, st
ruct rq *busiest,
unsigned long total_load_moved = 0;
int this_best_prio = this_rq->curr->prio;
+ update_aggregate(this_cpu, sd);
+
do {
total_load_moved +=
class->load_balance(this_rq, this_cpu, busiest,
and
@@ -1169,7 +1168,10 @@ static unsigned long wakeup_gran(struct sched_entity *se)
* More easily preempt - nice tasks, while not making it harder for
* + nice tasks.
*/
- gran = calc_delta_asym(sysctl_sched_wakeup_granularity, se);
+ if (sched_feat(ASYM_GRAN))
+ gran = calc_delta_asym(sysctl_sched_wakeup_granularity, se);
+ else
+ gran = calc_delta_fair(sysctl_sched_wakeup_granularity, se);
return gran;
}
the asym logic is wrong wrt shares - it should look at tg->weight
next prev parent reply other threads:[~2008-05-14 15:13 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 2:06 volanoMark regression with kernel 2.6.26-rc1 Zhang, Yanmin
2008-05-06 5:41 ` Zhang, Yanmin
2008-05-06 11:52 ` Dhaval Giani
2008-05-07 17:33 ` Dhaval Giani
2008-05-08 5:18 ` Zhang, Yanmin
2008-05-08 5:32 ` Dhaval Giani
2008-05-08 5:40 ` Dhaval Giani
2008-05-08 5:53 ` Zhang, Yanmin
2008-05-08 6:04 ` Dhaval Giani
2008-05-08 6:11 ` Srivatsa Vaddagiri
2008-05-09 15:52 ` Srivatsa Vaddagiri
2008-05-09 15:54 ` Srivatsa Vaddagiri
2008-05-12 1:39 ` Zhang, Yanmin
2008-05-12 2:04 ` Dhaval Giani
2008-05-12 2:37 ` Srivatsa Vaddagiri
2008-05-12 3:33 ` Zhang, Yanmin
2008-05-12 4:52 ` Srivatsa Vaddagiri
2008-05-12 5:02 ` Zhang, Yanmin
2008-05-12 5:43 ` Zhang, Yanmin
2008-05-12 9:04 ` Mike Galbraith
2008-05-12 9:20 ` Peter Zijlstra
2008-05-14 9:22 ` Zhang, Yanmin
2008-05-14 13:44 ` Srivatsa Vaddagiri
2008-05-14 14:50 ` Mike Galbraith
2008-05-14 15:12 ` Peter Zijlstra [this message]
2008-05-15 8:20 ` Srivatsa Vaddagiri
2008-05-15 8:41 ` Peter Zijlstra
2008-05-15 17:10 ` Srivatsa Vaddagiri
2008-05-07 7:04 ` Andrew Morton
2008-05-07 9:17 ` Ingo Molnar
2008-05-07 9:33 ` Zhang, Yanmin
2008-05-07 17:34 ` Peter Zijlstra
2008-05-07 18:58 ` Peter Zijlstra
2008-05-08 6:07 ` Zhang, Yanmin
2008-05-08 5:20 ` Zhang, Yanmin
2008-05-08 5:34 ` Dhaval Giani
2008-05-08 6:43 ` Peter Zijlstra
2008-05-07 17:42 ` Dhaval Giani
2008-05-08 5:21 ` Zhang, Yanmin
2008-05-08 5:39 ` Dhaval Giani
2008-05-08 6:03 ` Zhang, Yanmin
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=1210777967.10126.17.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=dhaval@linux.vnet.ibm.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=vatsa@linux.vnet.ibm.com \
--cc=yanmin_zhang@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox