From: David Howells <dhowells@redhat.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Matthew Wilcox <matthew@wil.cx>,
torvalds@osdl.org, akpm@osdl.org, sfr@canb.auug.org.au,
linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH 1/4] LOG2: Implement a general integer log2 facility in the kernel [try #4]
Date: Mon, 09 Oct 2006 11:11:36 +0100 [thread overview]
Message-ID: <7795.1160388696@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0610061015570.14591@schroedinger.engr.sgi.com>
Christoph Lameter <clameter@sgi.com> wrote:
> Why so complicated and why do it at all? We already have fls and ffs
> amoung the bit operations and those map to cpu instructions on arches
> that support these. fls can be used as a log 2 facilities. If you need
> another name and further refine it then just add an inline function.
There are a number of reasons:
(1) There are a bunch of independent log2 implementations lying around in the
code. It'd be nice to just have one set that anyone can use.
(2) Not everyone realises that fls() can be used to do log2().
(3) ilog2(n) != fls(n)
This means that the asm-optimised version for one might be less optimal
for the other (for example, ilog2() produces an undefined result if n <=
1, fls() must return 0).
(4) There are occasions when you might want to take a log2 of a constant.
With the totally inline asm approach, it would always execute some code,
though it should be unnecessary. What I've done permits you to avoid that
as the answer is always going to be the same.
(5) fls() and fls64() can't be used to initialise a variable at compile time,
ilog2() can.
David
next prev parent reply other threads:[~2006-10-09 10:11 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 13:34 [PATCH 1/4] LOG2: Implement a general integer log2 facility in the kernel [try #4] David Howells
2006-10-06 13:34 ` [PATCH 2/4] LOG2: Alter roundup_pow_of_two() so that it can use a ilog2() on a constant " David Howells
2006-10-06 13:34 ` [PATCH 3/4] LOG2: Alter get_order() so that it can make use of " David Howells
2006-10-06 13:34 ` [PATCH 4/4] LOG2: Provide ilog2() fallbacks for powerpc " David Howells
2006-10-06 14:17 ` [PATCH 1/4] LOG2: Implement a general integer log2 facility in the kernel " Matthew Wilcox
2006-10-06 14:33 ` David Howells
2006-10-06 17:17 ` Christoph Lameter
2006-10-09 10:11 ` David Howells [this message]
2006-10-09 11:06 ` Christoph Lameter
2006-10-09 12:09 ` David Howells
2006-10-09 17:17 ` Christoph Lameter
2006-10-10 9:58 ` David Howells
2006-10-06 20:33 ` Jan Engelhardt
2006-10-06 20:39 ` Matthew Wilcox
2006-10-06 20:52 ` Jan Engelhardt
2006-10-09 8:06 ` David Howells
2006-10-09 8:36 ` Jan Engelhardt
2006-10-09 9:51 ` Kyle Moffett
2006-10-09 10:26 ` Arnd Bergmann
2006-10-09 10:32 ` Stephen Rothwell
2006-10-09 12:20 ` Jan Engelhardt
2006-10-09 12:54 ` David Howells
2006-10-09 20:00 ` Jan Engelhardt
2006-10-09 20:36 ` Andreas Schwab
2006-10-10 9:41 ` Jan Engelhardt
2006-10-10 11:42 ` Arnd Bergmann
2006-10-09 13:09 ` Geert Uytterhoeven
2006-10-09 14:52 ` Arnd Bergmann
2006-10-09 15:05 ` Geert Uytterhoeven
2006-10-09 15:27 ` Arnd Bergmann
2006-10-09 15:31 ` Geert Uytterhoeven
2006-10-09 16:47 ` Arnd Bergmann
2006-10-10 7:55 ` David Woodhouse
2006-10-10 12:12 ` Arnd Bergmann
2006-10-10 12:23 ` David Howells
2006-10-07 23:50 ` Roman Zippel
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=7795.1160388696@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@osdl.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