lhash(3) OpenSL lhash(3)
NAME
lhnew, lhfree, lhinsert, lhdelete, lhretrieve, lhdoall,
lhdoallarg, lherror - dynamic hash table
SYNOPSIS
#include
LHASH *lhnew(LHASHASHFNTYPE hash, LHASHCOMPFNTYPE compare);
void lhfree(LHASH *table);
void *lhinsert(LHASH *table, void *data);
void *lhdelete(LHASH *table, void *data);
void *lhretrieve(LHASH *table, void *data);
void lhdoall(LHASH *table, LHASHDOALFNTYPE func);
void lhdoallarg(LHASH *table, LHASHDOALARGFNTYPE func,
void *arg);
int lherror(LHASH *table);
typedef int (*LHASHCOMPFNTYPE)(const void *, const void *);
typedef unsigned long (*LHASHASHFNTYPE)(const void *);
typedef void (*LHASHDOALFNTYPE)(const void *);
typedef void (*LHASHDOALARGFNTYPE)(const void *, const void *);
DESCRIPTION
This library implements dynamic hash tables. The hash table entries can
be arbitrary structures. Usually they consist of key and value fields.
lhnew() creates a new LHASH structure to store arbitrary data entries,
and provides the 'hash' and 'compare' callbacks to be used in organis-
ing the table's entries. The hash callback takes a pointer to a table
entry as its argument and returns an unsigned long hash value for its
key field. The hash value is normally truncated to a power of 2, so
make sure that your hash function returns well mixed low order bits.
The compare callback takes two arguments (pointers to two hash table
entries), and returns 0 if their keys are equal, non-zero otherwise.
If your hash table will contain items of some particular type and the
hash and compare callbacks hash/compare these types, then the
DECLARELHASHASHFN and IMPLEMENTLHASHCOMPFN macros can be used to
create callback wrappers of the prototypes required by lhnew(). These
provide per-variable casts before calling the type-specific callbacks
written by the application author. These macros, as well as those used
for the "doall" callbacks, are defined as;
#define DECLARELHASHASHFN(fname,otype) \
unsigned long fname##LHASHASH(const void *);
#define IMPLEMENTLHASHASHFN(fname,otype) \
unsigned long fname##LHASHASH(const void *arg) { \
otype a = (otype)arg; \
return fname(a); }
#define LHASHASHFN(fname) fname##LHASHASH
#define DECLARELHASHCOMPFN(fname,otype) \
int fname##LHASHCOMP(const void *, const void *);
#define IMPLEMENTLHASHCOMPFN(fname,otype) \
int fname##LHASHCOMP(const void *arg1, const void *arg2) { \
otype a = (otype)arg1; \
otype b = (otype)arg2; \
return fname(a,b); }
#define LHASHCOMPFN(fname) fname##LHASHCOMP
#define DECLARELHASHDOALFN(fname,otype) \
void fname##LHASHDOAL(const void *);
#define IMPLEMENTLHASHDOALFN(fname,otype) \
void fname##LHASHDOAL(const void *arg) { \
otype a = (otype)arg; \
fname(a); }
#define LHASHDOALFN(fname) fname##LHASHDOAL
#define DECLARELHASHDOALARGFN(fname,otype,atype) \
void fname##LHASHDOALARG(const void *, const void *);
#define IMPLEMENTLHASHDOALARGFN(fname,otype,atype) \
void fname##LHASHDOALARG(const void *arg1, const void *arg2) { \
otype a = (otype)arg1; \
atype b = (atype)arg2; \
fname(a,b); }
#define LHASHDOALARGFN(fname) fname##LHASHDOALARG
An example of a hash table storing (pointers to) structures of type
'STUF' could be defined as follows;
/* Calculates the hash value of 'tohash' (implemented elsewhere) */
unsigned long STUFhash(const STUF *tohash);
/* Orders 'arg1' and 'arg2' (implemented elsewhere) */
int STUFcmp(const STUF *arg1, const STUF *arg2);
/* Create the type-safe wrapper functions for use in the LHASH internals */
static IMPLEMENTLHASHASHFN(STUFhash, const STUF *)
static IMPLEMENTLHASHCOMPFN(STUFcmp, const STUF *);
/* ... */
int main(int argc, char *argv[]) {
/* Create the new hash table using the hash/compare wrappers */
LHASH *hashtable = lhnew(LHASHASHFN(STUFhash),
LHASHCOMPFN(STUFcmp));
/* ... */
}
lhfree() frees the LHASH structure table. Allocated hash table entries
will not be freed; consider using lhdoall() to deallocate any remain-
ing entries in the hash table (see below).
lhinsert() inserts the structure pointed to by data into table. If
there already is an entry with the same key, the old value is replaced.
Note that lhinsert() stores pointers, the data are not copied.
lhdelete() deletes an entry from table.
lhretrieve() looks up an entry in table. Normally, data is a structure
with the key field(s) set; the function will return a pointer to a
fully populated structure.
lhdoall() will, for every entry in the hash table, call func with the
data item as its parameter. For lhdoall() and lhdoallarg(), func-
tion pointer casting should be avoided in the callbacks (see NOTE) -
instead, either declare the callbacks to match the prototype required
in lhnew() or use the declare/implement macros to create type-safe
wrappers that cast variables prior to calling your type-specific call-
backs. An example of this is illustrated here where the callback is
used to cleanup resources for items in the hash table prior to the
hashtable itself being deallocated:
/* Cleans up resources belonging to 'a' (this is implemented elsewhere) */
void STUFcleanup(STUF *a);
/* Implement a prototype-compatible wrapper for "STUFcleanup" */
IMPLEMENTLHASHDOALFN(STUFcleanup, STUF *)
/* ... then later in the code ... */
/* So to run "STUFcleanup" against all items in a hash table ... */
lhdoall(hashtable, LHASHDOALFN(STUFcleanup));
/* Then the hash table itself can be deallocated */
lhfree(hashtable);
When doing this, be careful if you delete entries from the hash table
in your callbacks: the table may decrease in size, moving the item that
you are currently on down lower in the hash table - this could cause
some entries to be skipped during the iteration. The second best solu-
tion to this problem is to set hash->download=0 before you start
(which will stop the hash table ever decreasing in size). The best
solution is probably to avoid deleting items from the hash table inside
a "doall" callback!
lhdoallarg() is the same as lhdoall() except that func will be
called with arg as the second argument and func should be of type
LHASHDOALARGFNTYPE (a callback prototype that is passed both the
table entry and an extra argument). As with lhdoall(), you can
instead choose to declare your callback with a prototype matching the
types you are dealing with and use the declare/implement macros to cre-
ate compatible wrappers that cast variables before calling your type-
specific callbacks. An example of this is demonstrated here (printing
all hash table entries to a BIO that is provided by the caller):
/* Prints item 'a' to 'outputbio' (this is implemented elsewhere) */
void STUFprint(const STUF *a, BIO *outputbio);
/* Implement a prototype-compatible wrapper for "STUFprint" */
static IMPLEMENTLHASHDOALARGFN(STUFprint, const STUF *, BIO *)
/* ... then later in the code ... */
/* Print out the entire hashtable to a particular BIO */
lhdoallarg(hashtable, LHASHDOALARGFN(STUFprint), loggingbio);
lherror() can be used to determine if an error occurred in the last
operation. lherror() is a macro.
RETURN VALUES
lhnew() returns NUL on error, otherwise a pointer to the new LHASH
structure.
When a hash table entry is replaced, lhinsert() returns the value
being replaced. NUL is returned on normal operation and on error.
lhdelete() returns the entry being deleted. NUL is returned if there
is no such value in the hash table.
lhretrieve() returns the hash table entry if it has been found, NUL
otherwise.
lherror() returns 1 if an error occurred in the last operation, 0 oth-
erwise.
lhfree(), lhdoall() and lhdoallarg() return no values.
NOTE
The various LHASH macros and callback types exist to make it possible
to write type-safe code without resorting to function-prototype casting
- an evil that makes application code much harder to audit/verify and
also opens the window of opportunity for stack corruption and other
hard-to-find bugs. It also, apparently, violates ANSI-C.
The LHASH code regards table entries as constant data. As such, it
internally represents lhinsert()'d items with a "const void *" pointer
type. This is why callbacks such as those used by lhdoall() and
lhdoallarg() declare their prototypes with "const", even for the
parameters that pass back the table items' data pointers - for consis-
tency, user-provided data is "const" at all times as far as the LHASH
code is concerned. However, as callers are themselves providing these
pointers, they can choose whether they too should be treating all such
parameters as constant.
As an example, a hash table may be maintained by code that, for reasons
of encapsulation, has only "const" access to the data being indexed in
the hash table (ie. it is returned as "const" from elsewhere in their
code) - in this case the LHASH prototypes are appropriate as-is. Con-
versely, if the caller is responsible for the life-time of the data in
question, then they may well wish to make modifications to table item
passed back in the lhdoall() or lhdoallarg() callbacks (see the
"STUFcleanup" example above). If so, the caller can either cast the
"const" away (if they're providing the raw callbacks themselves) or use
the macros to declare/implement the wrapper functions without "const"
types.
Callers that only have "const" access to data they're indexing in a ta-
ble, yet declare callbacks without constant types (or cast the "const"
away themselves), are therefore creating their own risks/bugs without
being encouraged to do so by the API. On a related note, those audit-
ing code should pay special attention to any instances of
DECLARE/IMPLEMENTLHASHDOAL[ARG]FN macros that provide types with-
out any "const" qualifiers.
BUGS
lhinsert() returns NUL both for success and error.
INTERNALS
The following description is based on the SLeay documentation:
The lhash library implements a hash table described in the Communica-
tions of the ACM in 1991. What makes this hash table different is that
as the table fills, the hash table is increased (or decreased) in size
via OPENSLrealloc(). When a 'resize' is done, instead of all hashes
being redistributed over twice as many 'buckets', one bucket is split.
So when an 'expand' is done, there is only a minimal cost to redis-
tribute some values. Subsequent inserts will cause more single
'bucket' redistributions but there will never be a sudden large cost
due to redistributing all the 'buckets'.
The state for a particular hash table is kept in the LHASH structure.
The decision to increase or decrease the hash table size is made
depending on the 'load' of the hash table. The load is the number of
items in the hash table divided by the size of the hash table. The
default values are as follows. If (hash->upload < load) => expand.
if (hash->download > load) => contract. The upload has a default
value of 1 and download has a default value of 2. These numbers can
be modified by the application by just playing with the upload and
download variables. The 'load' is kept in a form which is multiplied
by 256. So hash->upload=8*256; will cause a load of 8 to be set.
If you are interested in performance the field to watch is
numcompcalls. The hash library keeps track of the 'hash' value for
each item so when a lookup is done, the 'hashes' are compared, if there
is a match, then a full compare is done, and hash->numcompcalls is
incremented. If numcompcalls is not equal to numdelete plus
numretrieve it means that your hash function is generating hashes that
are the same for different values. It is probably worth changing your
hash function if this is the case because even if your hash table has
10 items in a 'bucket', it can be searched with 10 unsigned long com-
pares and 10 linked list traverses. This will be much less expensive
that 10 calls to your compare function.
lhstrhash() is a demo string hashing function:
unsigned long lhstrhash(const char *c);
Since the LHASH routines would normally be passed structures, this rou-
tine would not normally be passed to lhnew(), rather it would be used
in the function passed to lhnew().
SEE ALSO
lhstats(3)
HISTORY
The lhash library is available in all versions of SLeay and OpenSL.
lherror() was added in SLeay 0.9.1b.
This manpage is derived from the SLeay documentation.
In OpenSL 0.9.7, all lhash functions that were passed function point-
ers were changed for better type safety, and the function types
LHASHCOMPFNTYPE, LHASHASHFNTYPE, LHASHDOALFNTYPE and
LHASHDOALARGFNTYPE became available.
0.9.7l 2002-07-18 lhash(3)
|
