Taken directly from the threads FAQ . . . probably needs to by updated.
VendorOS versionThreads modelPOSIX APINotes
Digital Digital UNIX 4.0mixedD4, 1c
Digital UNIX 3.2kernel / boundD4
OpenVMS 7.0 (Alpha)see note 1D4, 1cuser model without patch kit
OpenVMS 7.0 (VAX)userD4, 1c
OpenVMS 6.2userD4
HP HP/UX 10.20??not yet announced
HP/UX 10.10userD4
IBM AIX 4.1 & 4.2kernelD4, D7
AIX 3.2.xuserDCE
OS/2kernelDCE
Linux Linux 1.2.13 and aboveuser / kernel1c, DCEsee free implementations for several packages
Linux 2.xkerneln/aclone() interface
Microsoft Windows NT & 95kernelDCEDCE kits layer on top of WIN32 threads
SGI Irix 6.2mixedsee note 2sproc() is still kernel / bound
Irix 6.1kernel / boundn/asproc() interface only
Sun Solaris 2.5 and abovemixed / system / bound1c
Solaris 2.4mixed / system / boundD8available from Sun only upon request
Solaris 2.xmixed / system / boundn/aUI threads supported across all releases
SunOS 4.xusern/aLWP only
Threads modelMeaning
user
a purely user-level threads system, with threads multiplexed atop a "traditional" Unix-style process
kernel
threads are "kernel entities" with no context switches taking place in user mode

/ bound a thread may be explicitly bound to a particular processor
mixed
a mixed-mode scheduler where user threads are multiplexed across some number of LWPs

/ system threads have "system" contention scope (a user thread may be permanently bound to an LWP)

/ bound an LWP may be permanently bound to a particular processor
API Meaning
n/a no POSIX threads API provided
1c conforms to the POSIX 1003.1c-1995 threads API
DCE POSIX 1003.4a draft 4 API is available as part of the OSF DCE kit for the platform
D4 DCE threads (or something similar) is bundled with the system
D7 POSIX 1003.4a draft 7 API (similar to the final 1003.1c standard, but substantially different in some details)
D8 POSIX 1003.4a draft 8 API (identical in most respects to the 1003.1c standard, but with a few "gotchas")

If you have comments or suggestions, email me at sdybiec@humanfactor.com