Quoting Daniel Vetter (2017-07-19 13:54:57)
Blocking in a worker is ok,
but needlessly inefficient,
that's what the unbound_wq is for. And it unifies the paths between the blocking and nonblocking commit, giving me just one path where I have to implement the deadlock avoidance trickery in the next patch.
For reference, I did that the other way by moving it all over to fences. -Chris