From: David Laight <david.laight.linux@gmail.com>
To: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Nicolas Pitre <npitre@baylibre.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] math64: Provide an uprounding variant of mul_u64_u64_div_u64()
Date: Mon, 31 Mar 2025 19:53:57 +0100 [thread overview]
Message-ID: <20250331195357.012c221f@pumpkin> (raw)
In-Reply-To: <epuk3zijp2jt6jh72z3xi2wxneeunf5xx2h77kvim6xmzminwj@4saalgxu3enu>
On Mon, 31 Mar 2025 18:14:29 +0200
Uwe Kleine-König <u.kleine-koenig@baylibre.com> wrote:
> Hello,
>
> On Fri, Mar 21, 2025 at 01:18:13PM +0000, David Laight wrote:
> > On Wed, 19 Mar 2025 18:14:25 +0100
> > Uwe Kleine-König <u.kleine-koenig@baylibre.com> wrote:
> >
> > > This is needed (at least) in the pwm-stm32 driver. Currently the
> > > pwm-stm32 driver implements this function itself. This private
> > > implementation can be dropped as a followup of this patch.
> > >
> > > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@baylibre.com>
> > > ---
> > > include/linux/math64.h | 1 +
> > > lib/math/div64.c | 15 +++++++++++++++
> > > 2 files changed, 16 insertions(+)
> > >
> > > diff --git a/include/linux/math64.h b/include/linux/math64.h
> > > index 6aaccc1626ab..0c545b3ddaa5 100644
> > > --- a/include/linux/math64.h
> > > +++ b/include/linux/math64.h
> > > @@ -283,6 +283,7 @@ static inline u64 mul_u64_u32_div(u64 a, u32 mul, u32 divisor)
> > > #endif /* mul_u64_u32_div */
> > >
> > > u64 mul_u64_u64_div_u64(u64 a, u64 mul, u64 div);
> > > +u64 mul_u64_u64_div_u64_roundup(u64 a, u64 mul, u64 div);
> > >
> > > /**
> > > * DIV64_U64_ROUND_UP - unsigned 64bit divide with 64bit divisor rounded up
> > > diff --git a/lib/math/div64.c b/lib/math/div64.c
> > > index 5faa29208bdb..66beb669992d 100644
> > > --- a/lib/math/div64.c
> > > +++ b/lib/math/div64.c
> > > @@ -267,3 +267,18 @@ u64 mul_u64_u64_div_u64(u64 a, u64 b, u64 c)
> > > }
> > > EXPORT_SYMBOL(mul_u64_u64_div_u64);
> > > #endif
> > > +
> > > +#ifndef mul_u64_u64_div_u64_roundup
> > > +u64 mul_u64_u64_div_u64_roundup(u64 a, u64 b, u64 c)
> > > +{
> > > + u64 res = mul_u64_u64_div_u64(a, b, c);
> > > + /* Those multiplications might overflow but it doesn't matter */
> > > + u64 rem = a * b - c * res;
> > > +
> > > + if (rem)
> > > + res += 1;
> >
> > Ugg...
> > return (((unsigned __int128_t)a * b) + (c - 1)) / c;
> > nearly works (on 64bit) but needs a u64 div_128_64()
>
> Both mul_u64_u64_div_u64_roundup() and mul_u64_u64_div_u64() would not
> be needed if we had a 128 bit type and a corresponding division on all
> supported architectures.
True, but the compiler would be doing a 128 by 128 divide - which isn't
needed here.
But you can rework the code to add in the offset between the multiply
and divide - just needs a 'tweak' to mul_u64_u64_div_u64().
David
>
> So given we're not in that situation, I wonder if Andrew is still
> considering this patch or if someone else would pick up this patch?
>
> Best regards
> Uwe
next prev parent reply other threads:[~2025-03-31 18:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 17:14 [PATCH] math64: Provide an uprounding variant of mul_u64_u64_div_u64() Uwe Kleine-König
2025-03-19 19:38 ` Nicolas Pitre
2025-03-20 7:36 ` Uwe Kleine-König
2025-03-21 13:18 ` David Laight
2025-03-31 16:14 ` Uwe Kleine-König
2025-03-31 18:53 ` David Laight [this message]
2025-04-01 7:25 ` Uwe Kleine-König
2025-04-01 19:26 ` David Laight
2025-04-01 20:13 ` Nicolas Pitre
2025-04-01 20:30 ` Nicolas Pitre
2025-04-01 21:37 ` David Laight
2025-04-01 22:10 ` Nicolas Pitre
2025-04-02 8:16 ` Uwe Kleine-König
2025-04-02 12:52 ` David Laight
2025-04-02 15:01 ` Uwe Kleine-König
2025-04-02 20:59 ` David Laight
2025-04-03 6:08 ` Uwe Kleine-König
2025-04-02 21:46 ` David Laight
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=20250331195357.012c221f@pumpkin \
--to=david.laight.linux@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npitre@baylibre.com \
--cc=u.kleine-koenig@baylibre.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