diff options
author | Brian Behlendorf <[email protected]> | 2010-11-30 09:51:46 -0800 |
---|---|---|
committer | Brian Behlendorf <[email protected]> | 2010-12-07 10:02:32 -0800 |
commit | 9fe45dc1ac5d0292a69cc91f951b984f21ae0aaa (patch) | |
tree | 0cbdf3b6bdfe69319f57de462f16ddd0fe7197a9 /include/sys/thread.h | |
parent | 8beea9ac2428bd3b4652e484f46726e0a261523a (diff) |
Add Thread Specific Data (TSD) Implementation
Thread specific data has implemented using a hash table, this avoids
the need to add a member to the task structure and allows maximum
portability between kernels. This implementation has been optimized
to keep the tsd_set() and tsd_get() times as small as possible.
The majority of the entries in the hash table are for specific tsd
entries. These entries are hashed by the product of their key and
pid because by design the key and pid are guaranteed to be unique.
Their product also has the desirable properly that it will be uniformly
distributed over the hash bins providing neither the pid nor key is zero.
Under linux the zero pid is always the init process and thus won't be
used, and this implementation is careful to never to assign a zero key.
By default the hash table is sized to 512 bins which is expected to
be sufficient for light to moderate usage of thread specific data.
The hash table contains two additional type of entries. They first
type is entry is called a 'key' entry and it is added to the hash during
tsd_create(). It is used to store the address of the destructor function
and it is used as an anchor point. All tsd entries which use the same
key will be linked to this entry. This is used during tsd_destory() to
quickly call the destructor function for all tsd associated with the key.
The 'key' entry may be looked up with tsd_hash_search() by passing the
key you wish to lookup and DTOR_PID constant as the pid.
The second type of entry is called a 'pid' entry and it is added to the
hash the first time a process set a key. The 'pid' entry is also used
as an anchor and all tsd for the process will be linked to it. This
list is using during tsd_exit() to ensure all registered destructors
are run for the process. The 'pid' entry may be looked up with
tsd_hash_search() by passing the PID_KEY constant as the key, and
the process pid. Note that tsd_exit() is called by thread_exit()
so if your using the Solaris thread API you should not need to call
tsd_exit() directly.
Diffstat (limited to 'include/sys/thread.h')
-rw-r--r-- | include/sys/thread.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/include/sys/thread.h b/include/sys/thread.h index 06db6d4c9..c5f4234da 100644 --- a/include/sys/thread.h +++ b/include/sys/thread.h @@ -31,6 +31,7 @@ #include <linux/kthread.h> #include <sys/types.h> #include <sys/sysmacros.h> +#include <sys/tsd.h> /* * Thread interfaces |