Version: 1
-Previous: 62cdb077af8e2f663bf7e00b21ff7f4d274e25d5
-Head: 9e07c52086ff8e05c188591e97d5548d3dfc0578
+Previous: 54d528eaf74183c44350868171c616e43f6f41f6
+Head: 053b48ca7beab4dad63b6a4e6cf568f2e1f1a87c
Applied:
verbs-ext: 6fbf2b29ca68fc10b7ee47dc0c09f54db0b32320
compat-ex: fb8aa3e0b8ed628564d7d774907fd17a72a23522
xrcd: 71fa003681345f671bdef05c9548263252e949de
srq_ex: 9e07c52086ff8e05c188591e97d5548d3dfc0578
+ xrc_qp: 053b48ca7beab4dad63b6a4e6cf568f2e1f1a87c
Unapplied:
Hidden:
--- /dev/null
+Bottom: d98e2546482ad10f245503b04e53054423653799
+Top: d98e2546482ad10f245503b04e53054423653799
+Author: Sean Hefty <sean.hefty@intel.com>
+Date: 2012-09-17 16:00:12 -0700
+
+libibverbs: Add support for XRC QPs
+
+XRC queue pairs: xrc defines two new types of QPs. The
+initiator, or send-side, xrc qp behaves similar to a send-
+only RC qp. xrc send qp's are managed through the existing
+QP functions. The send_wr structure is extended in a back-
+wards compatible way to support posting sends on a send xrc
+qp, which require specifying the remote xrc srq.
+
+The target, or receive-side, xrc qp behaves differently
+than other implemented qp's. A recv xrc qp can be created,
+modified, and destroyed like other qp's through the existing
+calls. The qp_init_attr structure is extended for xrc qp's.
+
+Because xrc recv qp's are bound to an xrcd, rather than a pd,
+it is intended to be used among multiple processes. Any process
+with access to an xrcd may allocate and connect an xrc recv qp.
+The actual xrc recv qp is allocated and managed by the kernel.
+If the owning process explicit destroys the xrc recv qp, it is
+destroyed. However, if the xrc recv qp is left open when the
+user process exits or closes its device, then the lifetime of
+the xrc recv qp is bound with the lifetime of the xrcd.
+
+Signed-off-by: Sean Hefty <sean.hefty@intel.com>
+
+
+---
+
+