So I went ahead and applied this for 3.15, although I suspect the verbs API is probably the wrong one. I understand that the mlx5 microarchitecture requires some of this signature binding stuff to go through a work queue, but conceptually I don't think the IB_WR_REG_SIG_MR work request makes sense as the right interface. Why do I need to do both a synchronous create_mr and an asynchronous work request for what's conceptually a single operation? Similarly the ib_check_mr_status() operation doesn't really make sense to me as an additional synchronous operation -- why do I not just get signature information as part of the completion entry for the transaction that generated it? Anyway, you guys are the ones that will have to clean this up in the future when it becomes a problem, so I'm not going to push on this. - R. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
