From: Davidlohr Bueso <dave@stgolabs.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Anshul Garg <aksgarg1989@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
anshul.g@samsung.com
Subject: Re: [PATCH] lib/int_sqrt.c: Optimize square root function
Date: Mon, 02 Feb 2015 20:41:41 -0800 [thread overview]
Message-ID: <1422938501.2293.1.camel@stgolabs.net> (raw)
In-Reply-To: <CA+55aFxnq=QB0xAR1KW+25WcD+Z2aFrBhPa9oVhGr=PjqMTsmA@mail.gmail.com>
On Mon, 2015-02-02 at 11:13 -0800, Linus Torvalds wrote:
> IOW, instead of
>
> m = 1UL << (BITS_PER_LONG - 2);
>
> perhaps something like
>
> m = 1UL << (BITS_PER_LONG/2- 2);
> if (m < x)
> m <<= BITS_PER_LONG/2;
>
> (assuming gcc can change that code into a "cmov") might cut down the
> "lots of empty loops" case in half for small values of 'x'.
Makes a lot of sense.
> There's probably some other better cheap initial guess value estimator.
Just to get a feeling for the normal arg range in the non-driver parts
that use this thing:
fs/ceph/super.h: congestion_kb = (16*int_sqrt(totalram_pages)) << (PAGE_SHIFT-10);
fs/nfs/write.c: nfs_congestion_kb = (16*int_sqrt(totalram_pages)) << (PAGE_SHIFT-10);
fs/nfsd/nfscache.c: limit = (16 * int_sqrt(low_pages)) << (PAGE_SHIFT-10);
kernel/rcu/tree_plugin.h: ls = int_sqrt(nr_cpu_ids);
mm/memcontrol.c: inactive_ratio = int_sqrt(10 * gb);
mm/page_alloc.c: ratio = int_sqrt(10 * gb);
mm/page_alloc.c: new_min_free_kbytes = int_sqrt(lowmem_kbytes * 16);
So mostly values that scale according to mem or cpu.
next prev parent reply other threads:[~2015-02-03 4:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 17:12 [PATCH] lib/int_sqrt.c: Optimize square root function Anshul Garg
2015-02-02 19:00 ` Linus Torvalds
2015-02-02 19:13 ` Linus Torvalds
2015-02-03 4:41 ` Davidlohr Bueso [this message]
2015-02-03 4:57 ` Davidlohr Bueso
2015-02-03 15:54 ` Anshul Garg
2017-07-20 11:24 ` Peter Zijlstra
2017-07-20 11:52 ` Joe Perches
2017-07-20 14:13 ` Peter Zijlstra
2017-07-20 15:27 ` Peter Zijlstra
2017-07-20 18:31 ` Linus Torvalds
2017-07-20 22:34 ` Peter Zijlstra
2017-07-20 23:24 ` Linus Torvalds
2017-07-21 11:40 ` Peter Zijlstra
2017-07-21 12:15 ` Joe Perches
2017-07-21 13:26 ` Peter Zijlstra
2017-07-21 13:33 ` Peter Zijlstra
2015-02-03 4:47 ` Davidlohr Bueso
2015-02-03 15:42 ` Anshul Garg
2015-02-05 18:20 ` Linus Torvalds
2015-02-05 18:33 ` Linus Torvalds
2015-02-05 18:43 ` Anshul Garg
2015-02-05 19:37 ` Linus Torvalds
2015-02-08 15:39 ` Anshul Garg
2015-02-02 19:10 ` Joe Perches
2015-02-02 19:39 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2015-01-29 13:35 Anshul Garg
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=1422938501.2293.1.camel@stgolabs.net \
--to=dave@stgolabs.net \
--cc=aksgarg1989@gmail.com \
--cc=anshul.g@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.