On 06/03/2011 07:34 PM, Hefty, Sean wrote:
In order to support OFED or vendor specific calls, define a generic extension mechanism. This allows OFED, an RDMA vendor, or another registered 3rd party (for example, the librdmacm) to define RDMA extensions.
Will this mechanism allow an RDMA provider driver to export a new qp-related operation for use internally bit the supporting provider library? IE Not exposes to the RDMA application, but an internal interface between the library and driver. I have need for this with the T4 driver.
Users which make use extensions are aware that they are not only using an extended call, but are given information regarding how widely the extension by be supported.
Can you expand on the above sentence? I don't get the "how widely supported" angle? Steve. -- 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
