From: Paolo Bonzini <pbonzini@redhat.com>
To: Jocelyn Falempe <jfalempe@redhat.com>,
"Russell King (Oracle)" <linux@armlinux.org.uk>,
Christian Schrefl <chrisi.schrefl@gmail.com>
Cc: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
rust-for-linux <rust-for-linux@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: `u64` by `u64` div/mod in DRM QR for arm32
Date: Tue, 15 Apr 2025 14:50:26 +0200 [thread overview]
Message-ID: <5e0754a2-ba4e-454b-99cb-57c4ae99d020@redhat.com> (raw)
In-Reply-To: <1a03b57c-1b5f-405a-a22a-89cc82138c55@redhat.com>
On 4/15/25 11:14, Jocelyn Falempe wrote:
> For this case, the u64 divisor "pow" is a power of 10, so can have only
> a limited number of values. (17, and 9 of them can be used as u32).
> Normally when the divisor is known at build time the compiler can
> replace the division by a multiplication and some bit shift.
>
> so for 32bits machine, the match can be rewritten with constants, a bit
> like this:
If you add bindings to mul_u64_u64_shr from include/linux/math64.h, you
can include the constants yourself:
pub struct MagicMul {
mult: u64,
shift: u32,
}
// Computed using the algorithm from Hacker's Delight, 2nd ed.
const DIV10: [MagicMul; 19] = [
MagicMul { mult: 0x1, shift: 0 },
MagicMul { mult: 0x6666666666666667u64, shift: 66 },
MagicMul { mult: 0xA3D70A3D70A3D70Bu64, shift: 70 },
MagicMul { mult: 0x20C49BA5E353F7CFu64, shift: 71 },
MagicMul { mult: 0x346DC5D63886594Bu64, shift: 75 },
MagicMul { mult: 0x29F16B11C6D1E109u64, shift: 78 },
MagicMul { mult: 0x431BDE82D7B634DBu64, shift: 82 },
MagicMul { mult: 0xD6BF94D5E57A42BDu64, shift: 87 },
MagicMul { mult: 0x55E63B88C230E77Fu64, shift: 89 },
MagicMul { mult: 0x112E0BE826D694B3u64, shift: 90 },
MagicMul { mult: 0x036F9BFB3AF7B757u64, shift: 91 },
MagicMul { mult: 0x00AFEBFF0BCB24ABu64, shift: 92 },
MagicMul { mult: 0x232F33025BD42233u64, shift: 101 },
MagicMul { mult: 0x384B84D092ED0385u64, shift: 105 },
MagicMul { mult: 0x0B424DC35095CD81u64, shift: 106 },
MagicMul { mult: 0x480EBE7B9D58566Du64, shift: 112 },
MagicMul { mult: 0x39A5652FB1137857u64, shift: 115 },
MagicMul { mult: 0x5C3BD5191B525A25u64, shift: 119 },
MagicMul { mult: 0x12725DD1D243ABA1u64, shift: 120 },
];
const fn div10(val: u64, exp: u32) -> u64 {
let MagicMul { mult, shift } = DIV10[exp as usize];
mul_u64_u64_shr(val, mult, shift)
}
#[test]
fn test_div10() {
assert_eq!(div10(12345678, 0), 12345678);
assert_eq!(div10(12345678, 1), 1234567);
assert_eq!(div10(12345678, 2), 123456);
assert_eq!(div10(12345678, 3), 12345);
assert_eq!(div10(12345678, 4), 1234);
assert_eq!(div10(12345678, 5), 123);
assert_eq!(div10(12345678, 6), 12);
assert_eq!(div10(12345678, 7), 1);
assert_eq!(div10(9876543298765432, 8), 98765432);
assert_eq!(div10(9876543298765432, 9), 9876543);
assert_eq!(div10(9876543298765432, 10), 987654);
assert_eq!(div10(9876543298765432, 11), 98765);
assert_eq!(div10(9876543298765432, 12), 9876);
assert_eq!(div10(9876543298765432, 13), 987);
assert_eq!(div10(9876543298765432, 14), 98);
assert_eq!(div10(9876543298765432, 15), 9);
assert_eq!(div10(12349876543298765432, 16), 1234);
assert_eq!(div10(12349876543298765432, 17), 123);
assert_eq!(div10(12349876543298765432, 18), 12);
}
I tried the test in userspace with this implementation of the
function:
#![feature(bigint_helper_methods)]
const fn mul_u64_u64_shr(m: u64, n: u64, s: u32) -> u64 {
let (a, b) = m.widening_mul(n);
if s == 0 {
a
} else if s < 64 {
(a >> s) | (b << 64 - s)
} else {
b >> (s - 64)
}
}
HTH,
Paolo
next prev parent reply other threads:[~2025-04-15 12:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 18:14 `u64` by `u64` div/mod in DRM QR for arm32 Miguel Ojeda
2025-04-14 19:21 ` Christian Schrefl
2025-04-14 19:46 ` Russell King (Oracle)
2025-04-15 9:14 ` Jocelyn Falempe
2025-04-15 12:50 ` Paolo Bonzini [this message]
2025-05-05 7:37 ` Geert Uytterhoeven
2025-04-14 20:04 ` Miguel Ojeda
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=5e0754a2-ba4e-454b-99cb-57c4ae99d020@redhat.com \
--to=pbonzini@redhat.com \
--cc=arnd@arndb.de \
--cc=chrisi.schrefl@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jfalempe@redhat.com \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=rust-for-linux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.