From: Sam Ravnborg <sam@ravnborg.org>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [patch V4] lib: GCD: Use binary GCD algorithm instead of Euclidean
Date: Sat, 07 May 2016 11:23:56 +0000 [thread overview]
Message-ID: <20160507112308.GA2612@ravnborg.org> (raw)
In-Reply-To: <1462527763-15301-1-git-send-email-zengzhaoxiu@163.com>
> diff --git a/arch/sparc/Kconfig b/arch/sparc/Kconfig
> index 57ffaf2..ca675ed 100644
> --- a/arch/sparc/Kconfig
> +++ b/arch/sparc/Kconfig
> @@ -42,6 +42,7 @@ config SPARC
> select ODD_RT_SIGACTION
> select OLD_SIGSUSPEND
> select ARCH_HAS_SG_CHAIN
> + select CPU_NO_EFFICIENT_FFS
>
> config SPARC32
> def_bool !64BIT
sparc64 have an efficient ffs implementation.
We use run-time patching to use the proper version
depending on the actual sparc cpu.
As this is determinded at config time, then let the
sparc cpu that has the efficient ffs benefit from this.
In other words - select CPU_NO_EFFICIENT_FFS only for SPARC32.
Sam
prev parent reply other threads:[~2016-05-07 11:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 9:42 [patch V4] lib: GCD: Use binary GCD algorithm instead of Euclidean zengzhaoxiu
2016-05-06 23:00 ` Andrew Morton
2016-05-07 8:41 ` George Spelvin
2016-05-07 10:46 ` Andreas Schwab
2016-05-08 12:52 ` Zhaoxiu Zeng
2016-05-07 11:23 ` Sam Ravnborg [this message]
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=20160507112308.GA2612@ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-arm-kernel@lists.infradead.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).