>Provide refcount_t, an atomic_t like primitive built just for refcounting.
>It provides overflow and underflow checks as well as saturation semantics such 
>that when it overflows, we'll never attempt to free it again, ever.

>Peter do you have the changes to the refcount_t interface compare to the 
>version in this patch? 
>We are now starting working on atomic_t --> refcount_t conversions and it 
>would save a bit of work to have latest version from you that we can be based 
>upon. 

Oh, and if we define refcount_t to be just atomic_t underneath, what about the 
other atomic_long_t, local_t and atomic64_t cases when it is used for 
recounting? 
I don't feel good just simply changing them to become atomic_t under refcount_t 
wrapper..... 

Reply via email to