DTS Application Library
0.2.3
Application library containing referenced objects and interfaces to common libraries
|
lookup3.c, by Bob Jenkins, May 2006, Public Domain (Original Documentation) More...
Files | |
file | lookup3.c |
by Bob Jenkins, May 2006, Public Domain. | |
Macros | |
#define | JHASH_INITVAL 0xdeadbeef |
Default init value for hash functioneaster egg copied from <linux/jhash.h> More... | |
#define | jenhash(key, length, initval) hashlittle(key, length, (initval) ? initval : JHASH_INITVAL); |
Define jenhash as hashlittle on big endian it should be hashbig. More... | |
#define | HASH_LITTLE_ENDIAN 0 |
#define | HASH_BIG_ENDIAN 0 |
#define | hashsize(n) ((uint32_t)1<<(n)) |
#define | hashmask(n) (hashsize(n)-1) |
#define | rot(x, k) (((x)<<(k)) | ((x)>>(32-(k)))) |
#define | mix(a, b, c) |
mix 3 32-bit values reversibly More... | |
#define | final(a, b, c) |
final mixing of 3 32-bit values (a,b,c) into c More... | |
Functions | |
uint32_t | hashword (const uint32_t *k, size_t length, uint32_t initval) |
hash a variable-length key into a 32-bit value (Big Endian) More... | |
void | hashword2 (const uint32_t *k, size_t length, uint32_t *pc, uint32_t *pb) |
same as hashword(), but take two seeds and return two 32-bit values More... | |
uint32_t | hashlittle (const void *key, size_t length, uint32_t initval) |
hash a variable-length key into a 32-bit value (Little Endian) More... | |
void | hashlittle2 (const void *key, size_t length, uint32_t *pc, uint32_t *pb) |
return 2 32-bit hash values. More... | |
uint32_t | hashbig (const void *key, size_t length, uint32_t initval) |
This is the same as hashword() on big-endian machines. More... | |
lookup3.c, by Bob Jenkins, May 2006, Public Domain (Original Documentation)
------------------------------------------------------------------------------- lookup3.c, by Bob Jenkins, May 2006, Public Domain. These are functions for producing 32-bit hashes for hash table lookup. hashword(), hashlittle(), hashlittle2(), hashbig(), mix(), and final() are externally useful functions. Routines to test the hash are included if SELF_TEST is defined. You can use this free for any purpose. It's in the public domain. It has no warranty. You probably want to use hashlittle(). hashlittle() and hashbig() hash byte arrays. hashlittle() is is faster than hashbig() on little-endian machines. Intel and AMD are little-endian machines. On second thought, you probably want hashlittle2(), which is identical to hashlittle() except it returns two 32-bit hashes for the price of one. You could implement hashbig2() if you wanted but I haven't bothered here. If you want to find a hash of, say, exactly 7 integers, do a = i1; b = i2; c = i3; mix(a,b,c); a += i4; b += i5; c += i6; mix(a,b,c); a += i7; final(a,b,c); then use c as the hash value. If you have a variable length array of 4-byte integers to hash, use hashword(). If you have a byte array (like a character string), use hashlittle(). If you have several byte arrays, or a mix of things, see the comments above hashlittle(). Why is this so big? I read 12 bytes at a time into 3 4-byte integers, then mix those integers. This is fast (you can do a lot more thorough mixing with 12*3 instructions on 3 integers than you can with 3 instructions on 1 byte), but shoehorning those bytes into integers efficiently is messy. -------------------------------------------------------------------------------
#define final | ( | a, | |
b, | |||
c | |||
) |
final mixing of 3 32-bit values (a,b,c) into c
------------------------------------------------------------------------------- final -- final mixing of 3 32-bit values (a,b,c) into c Pairs of (a,b,c) values differing in only a few bits will usually produce values of c that look totally different. This was tested for * pairs that differed by one bit, by two bits, in any combination of top bits of (a,b,c), or in any combination of bottom bits of (a,b,c). * "differ" is defined as +, -, ^, or ~^. For + and -, I transformed the output delta to a Gray code (a^(a>>1)) so a string of 1's (as is commonly produced by subtraction) look like a single 1-bit difference. * the base values were pseudorandom, all zero but one bit set, or all zero plus a counter that starts at zero. These constants passed: 14 11 25 16 4 14 24 12 14 25 16 4 14 24 and these came close: 4 8 15 26 3 22 24 10 8 15 26 3 22 24 11 8 15 26 3 22 24 -------------------------------------------------------------------------------
#define HASH_LITTLE_ENDIAN 0 |
Definition at line 69 of file lookup3.c.
Referenced by hashlittle(), and hashlittle2().
#define jenhash | ( | key, | |
length, | |||
initval | |||
) | hashlittle(key, length, (initval) ? initval : JHASH_INITVAL); |
#define JHASH_INITVAL 0xdeadbeef |
#define mix | ( | a, | |
b, | |||
c | |||
) |
mix 3 32-bit values reversibly
------------------------------------------------------------------------------- mix -- mix 3 32-bit values reversibly. This is reversible, so any information in (a,b,c) before mix() is still in (a,b,c) after mix(). If four pairs of (a,b,c) inputs are run through mix(), or through mix() in reverse, there are at least 32 bits of the output that are sometimes the same for one pair and different for another pair. This was tested for: * pairs that differed by one bit, by two bits, in any combination of top bits of (a,b,c), or in any combination of bottom bits of (a,b,c). * "differ" is defined as +, -, ^, or ~^. For + and -, I transformed the output delta to a Gray code (a^(a>>1)) so a string of 1's (as is commonly produced by subtraction) look like a single 1-bit difference. * the base values were pseudorandom, all zero but one bit set, or all zero plus a counter that starts at zero. Some k values for my "a-=c; a^=rot(c,k); c+=b;" arrangement that satisfy this are 4 6 8 16 19 4 9 15 3 18 27 15 14 9 3 7 17 3 Well, "9 15 3 18 27 15" didn't quite get 32 bits diffing for "differ" defined as + with a one-bit base and a two-bit delta. I used http://burtleburtle.net/bob/hash/avalanche.html to choose the operations, constants, and arrangements of the variables. This does not achieve avalanche. There are input bits of (a,b,c) that fail to affect some output bits of (a,b,c), especially of a. The most thoroughly mixed value is c, but it doesn't really even achieve avalanche in c. This allows some parallelism. Read-after-writes are good at doubling the number of bits affected, so the goal of mixing pulls in the opposite direction as the goal of parallelism. I did what I could. Rotates seem to cost as much as shifts on every machine I could lay my hands on, and rotates are much kinder to the top and bottom bits, so I used rotates. -------------------------------------------------------------------------------
Definition at line 122 of file lookup3.c.
Referenced by hashbig(), hashlittle(), hashlittle2(), hashword(), and hashword2().
uint32_t hashbig | ( | const void * | key, |
size_t | length, | ||
uint32_t | initval | ||
) |
This is the same as hashword() on big-endian machines.
* hashbig(): * This is the same as hashword() on big-endian machines. It is different * from hashlittle() on all machines. hashbig() takes advantage of * big-endian byte ordering.
Definition at line 862 of file lookup3.c.
References HASH_BIG_ENDIAN, and mix.
uint32_t hashlittle | ( | const void * | key, |
size_t | length, | ||
uint32_t | initval | ||
) |
hash a variable-length key into a 32-bit value (Little Endian)
------------------------------------------------------------------------------- hashlittle() -- hash a variable-length key into a 32-bit value k : the key (the unaligned variable-length array of bytes) length : the length of the key, counting by bytes initval : can be any 4-byte value Returns a 32-bit value. Every bit of the key affects every bit of the return value. Two keys differing by one or two bits will have totally different hash values. The best hash table sizes are powers of 2. There is no need to do mod a prime (mod is sooo slow!). If you need less than 32 bits, use a bitmask. For example, if you need only 10 bits, do h = (h & hashmask(10)); In which case, the hash table should have hashsize(10) elements. If you are hashing n strings (uint8_t **)k, do it like this: for (i=0, h=0; i<n; ++i) h = hashlittle( k[i], len[i], h); By Bob Jenkins, 2006. bob_jenkins@burtleburtle.net. You may use this code any way you wish, private, educational, or commercial. It's free. Use for hash table lookup, or anything where one collision in 2^^32 is acceptable. Do NOT use for cryptographic purposes. -------------------------------------------------------------------------------
Definition at line 298 of file lookup3.c.
References HASH_LITTLE_ENDIAN, and mix.
void hashlittle2 | ( | const void * | key, |
size_t | length, | ||
uint32_t * | pc, | ||
uint32_t * | pb | ||
) |
return 2 32-bit hash values.
* hashlittle2: return 2 32-bit hash values * * This is identical to hashlittle(), except it returns two 32-bit hash * values instead of just one. This is good enough for hash table * lookup with 2^^64 buckets, or if you want a second hash if you're not * happy with the first, or if you want a probably-unique 64-bit ID for * the key. *pc is better mixed than *pb, so use *pc first. If you want * a 64-bit value do something like "*pc + (((uint64_t)*pb)<<32)".
Definition at line 574 of file lookup3.c.
References HASH_LITTLE_ENDIAN, and mix.
uint32_t hashword | ( | const uint32_t * | k, |
size_t | length, | ||
uint32_t | initval | ||
) |
hash a variable-length key into a 32-bit value (Big Endian)
-------------------------------------------------------------------- This works on all machines. To be useful, it requires -- that the key be an array of uint32_t's, and -- that the length be the number of uint32_t's in the key The function hashword() is identical to hashlittle() on little-endian machines, and identical to hashbig() on big-endian machines, except that the length has to be measured in uint32_ts rather than in bytes. hashlittle() is more complicated than hashword() only because hashlittle() has to dance around fitting the key bytes into registers. --------------------------------------------------------------------
Definition at line 182 of file lookup3.c.
References mix.
void hashword2 | ( | const uint32_t * | k, |
size_t | length, | ||
uint32_t * | pc, | ||
uint32_t * | pb | ||
) |
same as hashword(), but take two seeds and return two 32-bit values
-------------------------------------------------------------------- hashword2() -- same as hashword(), but take two seeds and return two 32-bit values. pc and pb must both be nonnull, and *pc and *pb must both be initialized with seeds. If you pass in (*pb)==0, the output (*pc) will be the same as the return value from hashword(). --------------------------------------------------------------------
Definition at line 229 of file lookup3.c.
References mix.