From: Peter Zijlstra <peterz@infradead.org>
To: Afzal Mohammed <afzal.mohd.ma@gmail.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH] sched,fair: Remove > u32 weight handling for delta
Date: Mon, 6 Jul 2015 13:44:30 +0200 [thread overview]
Message-ID: <20150706114430.GE3644@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1436150677-1818-1-git-send-email-afzal.mohd.ma@gmail.com>
On Mon, Jul 06, 2015 at 08:14:37AM +0530, Afzal Mohammed wrote:
> scaled down weight 'fact' would not be > u32 rather than unlikely as the
> values being passed for delta is either NICE_O_LOAD or the weight of the
> 'se' which would be a value that can be accomodated in a u32.
This needs a bit more on why se->load.weight must fit u32 (its true, but
not evident from this text).
> Remove the initial > u32 handling on 'fact'.
>
> 9dbdb15553239 ("sched/fair: Rework sched_fair time accounting") in
> addition to fixing the original issue of time moving backwards elsewhere
> in the code, handled delta > u32 case (due to NO_HZ_FULL) which brought
> in as it's part the change changed here.
Because the unsigned long weight is a u64 on 64bit..
Now as long as we never call __calc_delta() on a rq weight -- which is a
sum of weights and can indeed be larger than u32, we can indeed remove
this.
And I think we already assume such, see this story on why shift will
remain positive.
> The hunk being removed here
> would not make a difference to it as this is on scaled weight > u32.
> And pre-"9dbdb15553239" doesn't seem to have logical equivalent of hunk
> removed here either.
-ENOPARSE.
next prev parent reply other threads:[~2015-07-06 11:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 2:44 [PATCH] sched,fair: Remove > u32 weight handling for delta Afzal Mohammed
2015-07-06 11:44 ` Peter Zijlstra [this message]
2015-07-06 13:34 ` Afzal Mohammed
2015-07-06 14:39 ` Afzal Mohammed
2015-07-06 18:19 ` [PATCH v2] " Afzal Mohammed
2015-08-12 11:12 ` Afzal Mohammed
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=20150706114430.GE3644@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=afzal.mohd.ma@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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