64no_api, ///< For sequential operation. i.e. no threading. Usually one would use the constant platform_api, which is suitably declared as one of the threading models, below.
65MS_Win32, ///< Usually "heavy-weight" threads, e.g. x86, alpha.
66posix_pthreads, ///< Usually "heavy-weight" threads, e.g. x86, alpha, SPARC. On Solaris, Linux, etc.
67IBM_cyclops///< IBM BlueGene/[C|P] (or Cyclops), ~10^6-~10^9 lightweight threads, NUMA architecture.
98/// A namespace to hold various traits relating to selecting the specific specialisation of thread_pool they would like.
99/**
100 These parameters allow the users to choose a thread_pool that has the properties they would like. Note that not all combinations make sense, so will give compilation errors, as they are not implemented, and of the rest, some of those may not be implemented. Contact the author if you need a specific specialisation!
106/// The thread_pool owns a single queue into which input_work is placed & from which thread_wk_t is distributed.
107/**
108 Work stealing from the queue; the adding work to and removing work from the queue is the limiting resource, possibly lock-free or with some sort of lock_type, that may have some sort of anon_semaphore to indicate to waiting pool_threads that it contains work.