public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Afzal Mohammed <afzal.mohd.ma@gmail.com>
To: Peter Zijlstra <peterz@infradead.org>
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 20:09:20 +0530	[thread overview]
Message-ID: <20150706143920.GA2704@afzalpc> (raw)
In-Reply-To: <20150706133407.GA5861@afzalpc>

Hi,

On Mon, Jul 06, 2015 at 07:04:07PM +0530, Afzal Mohammed wrote:
> On Mon, Jul 06, 2015 at 01:44:30PM +0200, Peter Zijlstra wrote:
> > On Mon, Jul 06, 2015 at 08:14:37AM +0530, Afzal Mohammed wrote:

> > > 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.
> 
> Reading 9dbdb15553239 ("sched/fair: Rework sched_fair time
> accounting") again, realized that I am wrong on this, that was
> referring to the below statement removed in that commit,
> 
>         if (likely(weight > (1UL << SCHED_LOAD_RESOLUTION)))
>                 tmp = (u64)delta_exec * scale_load_down(weight);
> 
> earlier came to a reasoning that as scale_load_down(weight) was not
> separately typecasted, value above u32 would be discarded, that non
> parsable statement meant that weight > u32 was not considered. Since
> cast has precedence over multiply, that statement of mine was wrong.

I take that back, consider as though I have not mentioned anything
above :)

Regards
Afzal

  reply	other threads:[~2015-07-06 14:39 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
2015-07-06 13:34   ` Afzal Mohammed
2015-07-06 14:39     ` Afzal Mohammed [this message]
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=20150706143920.GA2704@afzalpc \
    --to=afzal.mohd.ma@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    /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