On Tue, Jun 19, 2012 at 1:21 AM, Jack Morgenstein <ja...@dev.mellanox.co.il> wrote: > For security reasons (i.e., to prevent guests from sending MADs to tunnel QPs > belonging to other guests), each proxy-tunnel qp pair is assigned a unique, > reserved, qkey. These qkeys are available only for proxy and tunnel qp's -- > if the guest tries to use these qkeys with other qp's, it will fail.
How does a guest OS know which Q_Key it's allowed to use? I understand you stick the reserved Q_Keys in the privileged Q_Key area (MSB set) so it's not an issue for applications but I don't understand how you can avoid breaking unlucky guest OSes. Part of my problem is I don't see anywhere that MLX4_RESERVED_QKEY_MASK is actually used in this patch... - R. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html