linux-kernel - Re: [PATCH] x86: Optimize find_next_(zero

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080311152303.GA21530@elte.hu>
Date:	Tue, 11 Mar 2008 16:23:03 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Alexander van Heukelum <heukelum@...lshack.com>
Cc:	Alexander van Heukelum <heukelum@...tmail.fm>,
	Andi Kleen <andi@...stfloor.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86: Optimize find_next_(zero_)bit for small
	constant-size bitmaps


* Alexander van Heukelum <heukelum@...lshack.com> wrote:

> > > +#endif /* CONFIG_GENERIC_FIND_NEXT_BIT */
> > 
> > there should be an #else here i think, which maps find_next_bit to 
> > __find_next_bit / etc.
> 
> No, that is intentional: architectures are expected to either set 
> CONFIG_GENERIC_FIND_NEXT_BIT, or provide their own implementation of 
> find_next_bit.

indeed, you are right.

> This version runs fine on qemu.

great - i've queued it up into x86.git.

	Ingo
--
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/