From: "H. Peter Anvin" <hpa@zytor.com>
To: David Howells <dhowells@redhat.com>
Cc: torvalds@osdl.org, akpm@osdl.org, benh@kernel.crashing.org,
linux-kernel@vger.kernel.org, johannes@sipsolutions.net
Subject: Re: [PATCH] Fix get_order() [try #2]
Date: Tue, 06 Mar 2007 10:39:36 -0800 [thread overview]
Message-ID: <45EDB568.1090008@zytor.com> (raw)
In-Reply-To: <20070306183426.10768.51800.stgit@warthog.cambridge.redhat.com>
David Howells wrote:
>
> /**
> + * ilog2_up - rounded up log of base 2 of 32-bit or a 64-bit unsigned value
> + * @n - parameter
> + *
> + * constant-capable log of base 2 calculation
> + * - this can be used to initialise global variables from constant data, hence
> + * the massive ternary operator construction
> + * - the result is rounded up
> + * - the result is undefined when n < 1
> + *
> + * selects the appropriately-sized optimised version depending on sizeof(n)
> + */
> +#define ilog2_up(n) ((n) == 1 ? 0 : ilog2((n) - 1) + 1)
> +
Why not just make it ((n) < 1 ? 0 : ...) and make it well-defined for
n == 0?
> +/**
> * roundup_pow_of_two - round the given value up to nearest power of two
> * @n - parameter
> *
> @@ -159,8 +175,8 @@ unsigned long __roundup_pow_of_two(unsigned long n)
> #define roundup_pow_of_two(n) \
> ( \
> __builtin_constant_p(n) ? ( \
> - (n == 1) ? 0 : \
> - (1UL << (ilog2((n) - 1) + 1)) \
> + (n == 1) ? 1 : \
> + (1UL << ilog2_up(n)) \
> ) : \
... then this can be just "1UL << ilog2_up(n)".
[Sorry about previous email. I got confused about what
roundup_pow_of_two() actually does.]
-hpa
next prev parent reply other threads:[~2007-03-06 18:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 18:34 [PATCH] Fix get_order() [try #2] David Howells
2007-03-06 18:37 ` H. Peter Anvin
2007-03-06 18:41 ` David Howells
2007-03-06 18:39 ` H. Peter Anvin [this message]
2007-03-06 18:47 ` David Howells
2007-03-06 18:51 ` H. Peter Anvin
2007-03-06 19:42 ` Alexey Dobriyan
2007-03-06 20:01 ` David Howells
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=45EDB568.1090008@zytor.com \
--to=hpa@zytor.com \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=dhowells@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--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