On 10/15/2015 12:13 PM, Parav Pandit wrote:
Just curious, why does WQ need to be bind to PD? Isn't ucontext sufficient? Or because kcontext doesn't exist, PD serves that role? Or Is this just manifestation of how hardware behave?
PD is an attribute of a work queue (i.e. send/receive queue), it's used by the hardware for security validation before scattering to a memory region. For that, an external WQ object needs a PD, letting the
hardware makes that validation.
Since you mentioned, "QP can be configured to use "external" WQ object", it might be worth to reuse the WQ across multiple QPs of different PD?
Correct, external WQ can be used across multiple QPs, in that case its PD is used by the hardware for security validation when it accesses to the MR, in that case the QP's PD is not in use.
Because MR and QP validation check has to happen among MR and actual QP and might not require that check against WQ.
No, in that case of an external WQ its PD is used and the QP's PD is not in use.
-- 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
