If this is 'better' then it should be on as much as possible, and I certianly
don't want to see kernel ULPs query caps and other pointless things when
they already, necessarily, deal with out of order.
Sure. Kernel ULPs and any other user ULPs can skip query caps.
No, they can't because only mlx5 accepts the new flag.
This is why inverting the flag in the kernel makes much more sense.
Can you guys explain why should a ULP even be exposed to this at all?
I can today issue RDMA writes to a single remote buffer in a pattern
that are not "in-order". From what I understand, the OOO relates to
mutliple packets of a _single_ RDMA transaction, which afair a
granularity that the ULP isn't (and shouldn't be) exposed to.
I do not really understand what a ULP should do with this knob...
It's really a topology variable, maybe it needs to sit in the
CM or something?
Please correct me if I'm completely off...
--
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
