- opt::stat - internal statistics. Available types: skip_list::stat, skip_list::empty_stat (the default)
\warning The skip-list requires up to 67 hazard pointers that may be critical for some GCs for which
- the guard count is limited (like as gc::HP, gc::HRC). Those GCs should be explicitly initialized with
+ the guard count is limited (like as \p gc::HP). Those GCs should be explicitly initialized with
hazard pointer enough: \code cds::gc::HP myhp( 67 ) \endcode. Otherwise an run-time exception may be raised
when you try to create skip-list object.
\note There are several specializations of \p %SkipListSet for each \p GC. You should include:
- - <tt><cds/intrusive/skip_list_hp.h></tt> for gc::HP garbage collector
- - <tt><cds/intrusive/skip_list_hrc.h></tt> for gc::HRC garbage collector
- - <tt><cds/intrusive/skip_list_ptb.h></tt> for gc::PTB garbage collector
+ - <tt><cds/intrusive/skip_list_hp.h></tt> for \p gc::HP garbage collector
+ - <tt><cds/intrusive/skip_list_dhp.h></tt> for \p gc::DHP garbage collector
- <tt><cds/intrusive/skip_list_nogc.h></tt> for \ref cds_intrusive_SkipListSet_nogc for persistent set
- <tt><cds/intrusive/skip_list_rcu.h></tt> for \ref cds_intrusive_SkipListSet_rcu "RCU type"
before end of the set. Therefore, such iteration is more suitable for debugging purpose only
Remember, each iterator object requires 2 additional hazard pointers, that may be
- a limited resource for \p GC like as gc::HP and gc::HRC (for gc::PTB the count of
+ a limited resource for \p GC like as \p gc::HP (for \p gc::PTB the count of
guards is unlimited).
The iterator class supports the following minimalistic interface: