Why invent a new API for the mutex locks?

Using mutex_t, mutex_lock(), mutex_unlock(), mutex_trylock, etc.
in the kernel seems easier to document, at least...
(and otherwise apparently has identical semantics)