From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Ken Chen <kenchen@google.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] sched: fix inconsistency when redistribute per-cpu tg->cfs_rq shares.
Date: Wed, 19 Nov 2008 20:19:19 +0100 [thread overview]
Message-ID: <1227122359.29743.54.camel@lappy.programming.kicks-ass.net> (raw)
In-Reply-To: <b040c32a0811182241r3cf5e7c7l25d3627c2265ead2@mail.gmail.com>
On Tue, 2008-11-18 at 22:41 -0800, Ken Chen wrote:
It just occurred to me that you lost the boost stuff.
The issue with the boost flag is that we have a different
tg->cfs_rq[cpu]->shares
than the actual
tg->cfs_se[cpu]->load.weight
So that the starvation shares don't count towards the total distributed
shares.
I guess this is an overestimate vs underestimate issue, you now
underestimate possibly pessimising your actual bandwidth.
> diff --git a/kernel/sched.c b/kernel/sched.c
> index 9b1e793..1ff78b6 100644
> --- a/kernel/sched.c
> +++ b/kernel/sched.c
> @@ -1473,27 +1473,13 @@ static void
> update_group_shares_cpu(struct task_group *tg, int cpu,
> unsigned long sd_shares, unsigned long sd_rq_weight)
> {
> - int boost = 0;
> unsigned long shares;
> unsigned long rq_weight;
>
> if (!tg->se[cpu])
> return;
>
> - rq_weight = tg->cfs_rq[cpu]->load.weight;
> -
> - /*
> - * If there are currently no tasks on the cpu pretend there is one of
> - * average load so that when a new task gets to run here it will not
> - * get delayed by group starvation.
> - */
> - if (!rq_weight) {
> - boost = 1;
> - rq_weight = NICE_0_LOAD;
> - }
> -
> - if (unlikely(rq_weight > sd_rq_weight))
> - rq_weight = sd_rq_weight;
> + rq_weight = tg->cfs_rq[cpu]->rq_weight;
>
> /*
> * \Sum shares * rq_weight
> @@ -1501,7 +1487,7 @@ update_group_shares_cpu
> * \Sum rq_weight
> *
> */
> - shares = (sd_shares * rq_weight) / (sd_rq_weight + 1);
> + shares = (sd_shares * rq_weight) / sd_rq_weight;
> shares = clamp_t(unsigned long, shares, MIN_SHARES, MAX_SHARES);
>
> if (abs(shares - tg->se[cpu]->load.weight) >
> @@ -1510,11 +1496,7 @@ update_group_shares_cpu
> unsigned long flags;
>
> spin_lock_irqsave(&rq->lock, flags);
> - /*
> - * record the actual number of shares, not the boosted amount.
> - */
> - tg->cfs_rq[cpu]->shares = boost ? 0 : shares;
> - tg->cfs_rq[cpu]->rq_weight = rq_weight;
> + tg->cfs_rq[cpu]->shares = shares;
>
> __set_se_shares(tg->se[cpu], shares);
> spin_unlock_irqrestore(&rq->lock, flags);
> @@ -1528,13 +1510,23 @@ update_group_shares_cpu
> */
> static int tg_shares_up(struct task_group *tg, void *data)
> {
> - unsigned long rq_weight = 0;
> + unsigned long weight, rq_weight = 0;
> unsigned long shares = 0;
> struct sched_domain *sd = data;
> int i;
>
> for_each_cpu_mask(i, sd->span) {
> - rq_weight += tg->cfs_rq[i]->load.weight;
> + /*
> + * If there are currently no tasks on the cpu pretend there
> + * is one of average load so that when a new task gets to
> + * run here it will not get delayed by group starvation.
> + */
> + weight = tg->cfs_rq[i]->load.weight;
> + if (!weight)
> + weight = NICE_0_LOAD;
> +
> + tg->cfs_rq[i]->rq_weight = weight;
> + rq_weight += weight;
> shares += tg->cfs_rq[i]->shares;
> }
>
> @@ -1544,9 +1536,6 @@ static int tg_shares_up
> if (!sd->parent || !(sd->parent->flags & SD_LOAD_BALANCE))
> shares = tg->shares;
>
> - if (!rq_weight)
> - rq_weight = cpus_weight(sd->span) * NICE_0_LOAD;
> -
> for_each_cpu_mask(i, sd->span)
> update_group_shares_cpu(tg, i, shares, rq_weight);
prev parent reply other threads:[~2008-11-19 20:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-19 6:41 Ken Chen
2008-11-19 16:47 ` Peter Zijlstra
2008-11-19 17:39 ` Ingo Molnar
2008-11-19 19:19 ` 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=1227122359.29743.54.camel@lappy.programming.kicks-ass.net \
--to=a.p.zijlstra@chello.nl \
--cc=kenchen@google.com \
--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
all inboxes | Powered by JetHome®