linux-kernel - Re: [PATCH] sched/fair: Fix fixed point arithmetic width for shares and effective load

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20160823205502.GX10153@twins.programming.kicks-ass.net>
Date:   Tue, 23 Aug 2016 22:55:02 +0200
From:   Peter Zijlstra <peterz@...radead.org>
To:     Paul Turner <pjt@...nel.org>
Cc:     Dietmar Eggemann <dietmar.eggemann@....com>,
        Ingo Molnar <mingo@...nel.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] sched/fair: Fix fixed point arithmetic width for shares
 and effective load

On Tue, Aug 23, 2016 at 01:40:01PM -0700, Paul Turner wrote:
> Independent of this patch:
>   When we initially introduced load scaling, it was ~uniform on every
> value.  Most of the current pain has come from, and will continue to
> come from, that with v2 of the load-tracking this is no longer the
> case.  We have a massive number of scaled and unscaled inputs floating
> around, many of them derived values (e.g. source_load above) which
> require chasing.
> 
> I propose we simplify this.

Yes please... I had been thinking of trying to use sparse to give the
different FP scales different types, but gave up real quick on that.