From: Peter Zijlstra <peterz@infradead.org>
To: Zhaoxiu Zeng <zhaoxiu.zeng@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@kernel.org>,
George Spelvin <linux@horizon.com>,
David Howells <dhowells@redhat.com>,
AKASHI Takahiro <takahiro.akashi@linaro.org>,
Josh Boyer <jwboyer@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] GCD: add binary GCD algorithm
Date: Fri, 15 Aug 2014 15:58:55 +0200 [thread overview]
Message-ID: <20140815135855.GG19379@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1408106956-12986-1-git-send-email-zhaoxiu.zeng@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1900 bytes --]
On Fri, Aug 15, 2014 at 08:49:16PM +0800, Zhaoxiu Zeng wrote:
> Because some architectures (alpha, armv6, etc.) don't provide hardware division,
> the mod operation is slow! Binary GCD algorithm uses simple arithmetic operations,
> it replaces division with arithmetic shifts, comparisons, and subtraction.
>
> Signed-off-by: Zhaoxiu Zeng <zhaoxiu.zeng@gmail.com>
> ---
> lib/Kconfig | 15 +++++++++++++++
> lib/gcd.c | 31 ++++++++++++++++++++++++++++++-
> 2 files changed, 45 insertions(+), 1 deletion(-)
>
> diff --git a/lib/Kconfig b/lib/Kconfig
> index a5ce0c7..80e8e54 100644
> --- a/lib/Kconfig
> +++ b/lib/Kconfig
> @@ -177,6 +177,21 @@ config CRC8
> when they need to do cyclic redundancy check according CRC8
> algorithm. Module will be called crc8.
>
> +#
> +# GCD
> +#
> +choice
> + prompt "GCD implementation"
> + default GCD_ALGO_EUCLIDEAN
> +
> +config GCD_ALGO_EUCLIDEAN
> + bool "Euclidean algorithm"
> +
> +config GCD_ALGO_BINARY
> + bool "Binary GCD algorithm (Stein's algorithm)"
> +
> +endchoice
Does this result in the user being asked which GCD algo he wants? If so,
I think that's bad.
> +#else
> + r = a | b;
> +
> + if (!a || !b)
> + return r;
> +
> + r = r ^ (r - 1);
> + if (!(a & r))
> + goto even_odd; /* a/c even, b/c odd */
> + if (!(b & r))
> + goto odd_even; /* a/c odd, b/c even */
> +
> + /* a/c and b/c both odd */
> + while (a != b) {
> + if (a > b) {
> + a -= b;
> +even_odd:
> + do
> + a >>= 1;
> + while (!(a & r));
> + } else {
> + b -= a;
> +odd_even:
> + do
> + b >>= 1;
> + while (!(b & r));
> + }
> + }
> +#endif
> return b;
> }
So I looked at wikipedia (I wasn't aware of this algorithm, clever
though), and am still somewhat puzzled by your 'r'.
What's 'wrong' with their iterative version, or what's better about your
'r' stuff?
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-08-15 13:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-15 12:49 [PATCH 1/1] GCD: add binary GCD algorithm Zhaoxiu Zeng
2014-08-15 13:58 ` Peter Zijlstra [this message]
2014-08-15 16:41 ` zhaoxiu.zeng
2014-08-15 21:53 ` George Spelvin
2014-08-15 20:16 ` George Spelvin
2014-08-15 21:32 ` Peter Zijlstra
2014-08-22 21:31 ` Andrew Morton
2014-08-22 22:36 ` George Spelvin
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=20140815135855.GG19379@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=jwboyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@horizon.com \
--cc=mingo@kernel.org \
--cc=takahiro.akashi@linaro.org \
--cc=zhaoxiu.zeng@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