From: Oleg Nesterov <oleg@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Fox <afox@redhat.com>,
Stephen Johnston <sjohnsto@redhat.com>,
linux-kernel@vger.kernel.org,
Stanislaw Gruszka <sgruszka@redhat.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH v2] sched/cputime: make scale_stime() more precise
Date: Wed, 20 May 2020 17:24:40 +0200 [thread overview]
Message-ID: <20200520152439.GC26470@redhat.com> (raw)
In-Reply-To: <20200519172506.GA317395@hirez.programming.kicks-ass.net>
On 05/19, Peter Zijlstra wrote:
>
> > The new implementation does the additional div64_u64_rem() but according
> > to my naive measurements it is faster on x86_64, much faster if rtime/etc
> > are big enough. See
> >
> > https://lore.kernel.org/lkml/20200123130541.GA30620@redhat.com/
>
> Right, so -m32 when ran on x86_64 CPUs isn't really fair, because then
> it still has hardware fls() for ilog2() and a massively fast mult and
> division instruction. Try and run this on a puny 32bit ARM that maybe
> has a hardware multiplier on.
OK,
> Anyway, how about we write it like the below and then when some puny
> architecture comes complaining we can use Linus' original algorithm for
> their arch implementation.
Sure, I am fine either way, but...
> +static inline u64 mul_u64_u64_div_u64(u64 a, u64 mul, u64 div)
> {
> u64 q;
>
> asm ("mulq %2; divq %3" : "=a" (q)
> - : "a" (a), "rm" ((u64)mul), "rm" ((u64)div)
> + : "a" (a), "rm" (mul), "rm" (div)
> : "rdx");
...
> +#ifndef mul_u64_u64_div_u64
> +static inline u64 mul_u64_u64_div_u64(u64 a, u64 b, u64 c)
> +{
> + u64 res = 0, div, rem;
> + int shift;
> +
> + /* can a * b overflow ? */
> + if (ilog2(a) + ilog2(b) > 62) {
> + /*
> + * (b * a) / c is equal to
> + *
> + * (b / c) * a +
> + * (b % c) * a / c
> + *
> + * if nothing overflows. Can the 1st multiplication
> + * overflow? Yes, but we do not care: this can only
> + * happen if the end result can't fit in u64 anyway.
> + *
> + * So the code below does
> + *
> + * res = (b / c) * a;
> + * b = b % c;
> + */
> + div = div64_u64_rem(b, c, &rem);
> + res = div * a;
> + b = rem;
> +
> + shift = ilog2(a) + ilog2(b) - 62;
> + if (shift > 0) {
> + /* drop precision */
> + b >>= shift;
> + c >>= shift;
> + if (!c)
> + return res;
> + }
> + }
> +
> + return res + div64_u64(a * b, c);
> +}
Note that according to my measurements the "asm" version is slower than
the generic code above when "a * b" doesn't fit u64.
Nevermind, I agree with your version. Will you send this patch or do you
want me to make V3 ?
Oleg.
next prev parent reply other threads:[~2020-05-20 15:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 13:18 [PATCH] sched/cputime: make scale_stime() more precise Oleg Nesterov
2019-07-18 13:21 ` Oleg Nesterov
2019-07-18 14:55 ` Oleg Nesterov
2019-07-19 11:03 ` Peter Zijlstra
2019-07-19 13:47 ` Peter Zijlstra
2019-07-19 14:37 ` Oleg Nesterov
2019-07-22 19:56 ` Peter Zijlstra
2019-07-23 14:00 ` Oleg Nesterov
2019-07-23 14:29 ` Oleg Nesterov
2019-07-19 14:03 ` Oleg Nesterov
2019-07-22 19:45 ` Peter Zijlstra
2019-07-22 10:52 ` Stanislaw Gruszka
2019-07-22 20:00 ` Peter Zijlstra
2019-07-23 9:37 ` Stanislaw Gruszka
2020-01-22 16:46 ` Oleg Nesterov
2020-01-23 13:05 ` Oleg Nesterov
2020-01-24 15:42 ` Oleg Nesterov
2020-01-27 12:28 ` [PATCH v2] " Oleg Nesterov
2020-05-15 17:24 ` Oleg Nesterov
2020-05-19 17:25 ` Peter Zijlstra
2020-05-19 18:33 ` Linus Torvalds
2020-05-19 18:42 ` Peter Zijlstra
2020-05-19 19:11 ` Peter Zijlstra
2020-05-19 19:51 ` Linus Torvalds
2020-05-20 15:24 ` Oleg Nesterov [this message]
2020-05-20 15:36 ` Peter Zijlstra
2020-05-20 20:10 ` Peter Zijlstra
2020-05-21 13:26 ` Oleg Nesterov
2020-06-16 12:21 ` [tip: sched/core] sched/cputime: Improve cputime_adjust() tip-bot2 for Oleg Nesterov
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=20200520152439.GC26470@redhat.com \
--to=oleg@redhat.com \
--cc=afox@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sgruszka@redhat.com \
--cc=sjohnsto@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).