Re: [PATCH RFC 0/2] Lockless update of reference count protected by spinlock

On 06/19/2013 12:50 PM, Waiman Long wrote: This patchset supports a generic mechanism to atomically update a reference count that is protected by a spinlock without actually acquiring the lock itself. If the update doesn't succeeed, the caller will have to acquire the lock and update the

Re: [PATCH RFC 0/2] Lockless update of reference count protected by spinlock

On 06/19/2013 12:50 PM, Waiman Long wrote: This patchset supports a generic mechanism to atomically update a reference count that is protected by a spinlock without actually acquiring the lock itself. If the update doesn't succeeed, the caller will have to acquire the lock and update the

[PATCH RFC 0/2] Lockless update of reference count protected by spinlock

This patchset supports a generic mechanism to atomically update a reference count that is protected by a spinlock without actually acquiring the lock itself. If the update doesn't succeeed, the caller will have to acquire the lock and update the reference count in the the old way. This will help

[PATCH RFC 0/2] Lockless update of reference count protected by spinlock

This patchset supports a generic mechanism to atomically update a reference count that is protected by a spinlock without actually acquiring the lock itself. If the update doesn't succeeed, the caller will have to acquire the lock and update the reference count in the the old way. This will help