The self BTL is different from any other BTL. Any memcpy operation done by this BTL is automatically protected behind the matching logic, and therefore does not require extra thread safety protection. A mutex in the self BTL is mostly a copy/paste mistake.
On Feb 8, 2012, at 17:57 , Christopher Yeoh wrote:
> I've noticed that the self btl does not do any locking. It has one
> lock defined but its not actually used anywhere.
> So I'm just wondering if that is an oversight or if there is a reason
> that we know for sure that there will never be concurrent access
> to that particular btl with threads enabled?
> devel mailing list