[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20071120122243.a737c8a8.akpm@linux-foundation.org>
Date: Tue, 20 Nov 2007 12:22:43 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Joe Perches <joe@...ches.com>
Cc: herbert@...dor.apana.org.au, torvalds@...ux-foundation.org,
linux-kernel@...r.kernel.org
Subject: Re: [KERNEL]: Avoid divide in IS_ALIGN
On Tue, 20 Nov 2007 10:17:15 -0800
Joe Perches <joe@...ches.com> wrote:
> On Tue, 2007-11-20 at 21:56 +0800, Herbert Xu wrote:
> > [KERNEL]: Avoid divide in IS_ALIGN
> > I was happy to discover the brand new IS_ALIGN macro and quickly
> > used it in my code. To my dismay I found that the generated code
> > used division to perform the test.
> > This patch fixes it by changing the % test to an &. This avoids
> > the division.
>
> Perhaps this should use is_power_of_2?
>
> #define IS_ALIGNED(x, a) \
> ({ typeof(x) _a = (typeof(x))(a); \
> is_power_of_2(_a) ? (((x) & (_a - 1)) == 0) \
> : (((x) % _a == 0); })
>
> gcc -o2/oS seems to do the right thing.
The other *ALIGN* macros in there are only good for power-of-2 alignments
so I guess Herbert's change is OK.
The whole thing's a bit crufty really - there's no reason why it _can't_
work on non-power-of-2 numbers 9via an implementation such as you suggest)
and there's no commentary in there explaining that this will presently
break things.
Those macros are sufficiently obscure, risky and undocumented as to make
them of dubious value IMO. I mean, anything which forces you to go and
stare at the definition for a while when reviewing a callsite isn't worth
it.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists