From: Andi Kleen <andi@firstfloor.org>
To: Joe Perches <joe@perches.com>
Cc: Andi Kleen <andi@firstfloor.org>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
davidlohr.bueso@hp.com, rafael.j.wysocki@intel.com,
lenb@kernel.org, Andi Kleen <ak@linux.intel.com>,
"anshul.g" <anshul.g@samsung.com>
Subject: Re: [PATCH] Optimize int_sqrt for small values for faster idle
Date: Thu, 28 Jan 2016 23:40:11 +0100 [thread overview]
Message-ID: <20160128224011.GL31686@two.firstfloor.org> (raw)
In-Reply-To: <1454019344.10099.54.camel@perches.com>
> This thread might be relevant:
>
> https://lkml.org/lkml/2015/2/2/600
>
> and perhaps using fls might still be a good approach.
Linus wrote:
>>>
We *probably* have some argument range that we care more about, which
is why I'd like to know what the profile is that triggered this
optimization, and what the common argument range is.
<<<
That's exactly what I did. Used perf probe to get the common
range and optimize for that.
-Andi
next prev parent reply other threads:[~2016-01-28 22:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 21:42 [PATCH] Optimize int_sqrt for small values for faster idle Andi Kleen
2016-01-28 22:04 ` kbuild test robot
2016-01-28 22:11 ` kbuild test robot
2016-01-28 22:15 ` Joe Perches
2016-01-28 22:40 ` Andi Kleen [this message]
2016-01-28 22:22 ` Joe Perches
2016-01-28 22:29 ` Eric Dumazet
2016-01-28 22:30 ` Andi Kleen
2016-01-29 3:59 ` Rafael J. Wysocki
2016-01-31 7:27 ` Thomas Rohwer
2016-02-01 21:25 ` Rasmus Villemoes
2016-02-01 21:36 ` Andi Kleen
2016-02-01 23:08 ` Rasmus Villemoes
2016-02-02 0:00 ` Andi Kleen
2016-02-02 0:36 ` Eric Dumazet
2016-02-02 20:46 ` Rasmus Villemoes
2016-02-02 21:30 ` Eric Dumazet
2017-07-20 10:10 ` Peter Zijlstra
2017-07-24 13:28 ` Eric Dumazet
2016-02-07 21:32 ` Rasmus Villemoes
2016-02-09 20:44 ` Andi Kleen
2016-02-10 13:31 ` Fengguang Wu
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=20160128224011.GL31686@two.firstfloor.org \
--to=andi@firstfloor.org \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=anshul.g@samsung.com \
--cc=davidlohr.bueso@hp.com \
--cc=joe@perches.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael.j.wysocki@intel.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 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.