From: Jonathan Cameron <jic23@kernel.org>
To: Matti Vaittinen <mazziesaccount@gmail.com>
Cc: Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>,
Lars-Peter Clausen <lars@metafoo.de>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: gts-helper: Fix division loop
Date: Sun, 7 Jan 2024 16:22:53 +0000 [thread overview]
Message-ID: <20240107162253.66c1f0f1@jic23-huawei> (raw)
In-Reply-To: <ZZZ7pJBGkTdFFqiY@dc78bmyyyyyyyyyyyyydt-3.rev.dnainternet.fi>
On Thu, 4 Jan 2024 11:34:28 +0200
Matti Vaittinen <mazziesaccount@gmail.com> wrote:
> The loop based 64bit division may run for a long time when dividend is a
> lot bigger than the divider. Replace the division loop by the
> div64_u64() which implementation may be significantly faster.
>
> Signed-off-by: Matti Vaittinen <mazziesaccount@gmail.com>
> Fixes: 38416c28e168 ("iio: light: Add gain-time-scale helpers")
Hmm. Fix or not perf improvement? I'm going to take the middle ground
and leave the fixes tag, but not rush this in.
So applied to the togreg branch of iio.git and for now just pushed out
as testing for 0-day etc to take a look before I rebase that tree after
rc1.
> ---
>
> I've implemented also a fixup series for supporting rounding of
> gains/scales:
> https://lore.kernel.org/lkml/37d3aa193e69577353d314e94463a08d488ddd8d.1701780964.git.mazziesaccount@gmail.com/
>
> That series does also remove the offending loop.
>
> We don't currently have any in-tree users of GTS helpers which would
> need the rounding support so pushing the rounding is not urgent (and I
> haven't heard of Subjahit whose driver required the rounding). Hence, we
> may want to only take this loop fix in for now (?) and reconsider
> rounding when someone need that.
>
> Jonathan, what's your take on this?
Agreed - let us wait for the rounding to have a user, but makes sense
to tidy this corner up in the meantime.
Thanks,
Jonathan
>
> drivers/iio/industrialio-gts-helper.c | 5 ++---
> 1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/iio/industrialio-gts-helper.c b/drivers/iio/industrialio-gts-helper.c
> index 7653261d2dc2..abcab2d38589 100644
> --- a/drivers/iio/industrialio-gts-helper.c
> +++ b/drivers/iio/industrialio-gts-helper.c
> @@ -34,7 +34,7 @@
> static int iio_gts_get_gain(const u64 max, const u64 scale)
> {
> u64 full = max;
> - int tmp = 1;
> + int tmp = 0;
>
> if (scale > full || !scale)
> return -EINVAL;
> @@ -48,8 +48,7 @@ static int iio_gts_get_gain(const u64 max, const u64 scale)
> tmp++;
> }
>
> - while (full > scale * (u64)tmp)
> - tmp++;
> + tmp += div64_u64(full, scale);
>
> return tmp;
> }
>
> base-commit: 2cc14f52aeb78ce3f29677c2de1f06c0e91471ab
next prev parent reply other threads:[~2024-01-07 16:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 9:34 [PATCH] iio: gts-helper: Fix division loop Matti Vaittinen
2024-01-07 16:22 ` Jonathan Cameron [this message]
2024-01-08 6:35 ` Matti Vaittinen
2024-01-19 11:56 ` Subhajit Ghosh
2024-01-22 6:50 ` Matti Vaittinen
2024-01-22 9:58 ` Subhajit Ghosh
2024-02-04 13:49 ` Subhajit Ghosh
2024-02-05 9:19 ` Matti Vaittinen
2024-01-22 16:27 ` David Laight
2024-01-22 19:24 ` Jonathan Cameron
2024-01-23 10:30 ` Matti Vaittinen
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=20240107162253.66c1f0f1@jic23-huawei \
--to=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matti.vaittinen@fi.rohmeurope.com \
--cc=mazziesaccount@gmail.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