From: Peter Zijlstra <peterz@infradead.org>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: mingo@elte.hu, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] sched: 64bit: fix overflow(was: fix divide by zero)
Date: Thu, 12 Jun 2008 10:50:34 +0200 [thread overview]
Message-ID: <1213260634.31518.88.camel@twins> (raw)
In-Reply-To: <4850E19B.1050202@cn.fujitsu.com>
On Thu, 2008-06-12 at 16:43 +0800, Lai Jiangshan wrote:
> (overflow means weight >= 2^32 here, because inv_weigh = 2^32/weight)
>
> A weight of a cfs_rq is the sum of weights of which entities
> are queued on this cfs_rq, so it will be overflow when entities
> are too many.
>
> Although, overflow is very hardly occurred, but it break fairness when
> it is occurred. And 64bits system have more memory than 32bits system
> and 64bits system can create more process usually, so overflow many be
> occurred more.
>
> This patch guarantee fairness when overflow in 64bits system.
> Thanks to the optimization of compiler, it change nothing in 32bits system.
Yeah,. bit sad for that one branch extra on 64-bit, but I get the
unlikely is as good as we can get it.
Acked-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
> Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
> ---
> diff --git a/kernel/sched.c b/kernel/sched.c
> index bfb8ad8..e277533 100644
> --- a/kernel/sched.c
> +++ b/kernel/sched.c
> @@ -1337,8 +1337,13 @@ calc_delta_mine(unsigned long delta_exec, unsigned long weight,
> {
> u64 tmp;
>
> - if (!lw->inv_weight)
> - lw->inv_weight = 1 + (WMULT_CONST-lw->weight/2)/(lw->weight+1);
> + if (!lw->inv_weight) {
> + if (BITS_PER_LONG > 32 && unlikely(lw->weight >= WMULT_CONST))
> + lw->inv_weight = 1;
> + else
> + lw->inv_weight = 1 + (WMULT_CONST-lw->weight/2)
> + / (lw->weight+1);
> + }
>
> tmp = (u64)delta_exec * weight;
> /*
>
>
>
>
prev parent reply other threads:[~2008-06-12 8:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 8:43 Lai Jiangshan
2008-06-12 8:50 ` 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=1213260634.31518.88.camel@twins \
--to=peterz@infradead.org \
--cc=laijs@cn.fujitsu.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®