bitops: remove "optimizations"
authorThomas Gleixner <tglx@linutronix.de>
Tue, 29 Apr 2008 10:01:02 +0000 (12:01 +0200)
committerLinus Torvalds <torvalds@linux-foundation.org>
Tue, 29 Apr 2008 15:11:16 +0000 (08:11 -0700)
commitfee4b19fb3f28d17c0b9f9ea0668db5275697178
tree0d7c34ef39cdac5a0c7f89376e85cc3ef621a7da
parent8972331292753c89dbdd10b175e999ce78dc3be7
bitops: remove "optimizations"

The mapsize optimizations which were moved from x86 to the generic
code in commit 64970b68d2b3ed32b964b0b30b1b98518fde388e increased the
binary size on non x86 architectures.

Looking into the real effects of the "optimizations" it turned out
that they are not used in find_next_bit() and find_next_zero_bit().

The ones in find_first_bit() and find_first_zero_bit() are used in a
couple of places but none of them is a real hot path.

Remove the "optimizations" all together and call the library functions
unconditionally.

Boot-tested on x86 and compile tested on every cross compiler I have.

Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
include/linux/bitops.h
lib/find_next_bit.c