Skip to contentSkip to conversation

libibverbs: Add support for XRC QPs

PATCH Shlomo Pongratz 2 participants 2 messages Mar 31, 2013 1 message not in the archive InfiniBand

lore
Share & tools
lore
#0 lore raw

Hi Sean,

Just wonder, the Infiniband Annex for XRC uses the terms "XRC INI QP" and "XRC TGT QP" and the kernel include file "include/rdma/ib_verbs.h" also defines "IB_QPT_XRC_INI" and "IB_QPT_XRC_TGT" so why to use in "include/infiniband/verbs.h" other names i.e. "IBV_QPT_XRC_SEND" and "IBV_QPT_XRC_RECV"? I agree that send and receive are more intuitive but I think that consistency is more important.

Best regards,

S.P.

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): 5157F642.9090004-VPRAkNaXOzVWk0Htik3J/[email protected]

#2 lore raw
Quoted 7 lines

Just wonder, the Infiniband Annex for XRC uses the terms "XRC INI QP" and "XRC TGT QP" and the kernel include file "include/rdma/ib_verbs.h" also defines "IB_QPT_XRC_INI" and "IB_QPT_XRC_TGT" so why to use in "include/infiniband/verbs.h" other names i.e. "IBV_QPT_XRC_SEND" and "IBV_QPT_XRC_RECV"?
I agree that send and receive are more intuitive but I think that consistency is more important.

A user space API should strive to be intuitive to use and save developers from having to read specs.

So, I'll disagree here.

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html