I'll have to look into that. So far, the library was intended as an add-on
to the existing code with the option to fall back to the original API if
need be.
Which of the features would you want to see in librdmacm? I guess the
integration of the cm_id and qp as well as the simpler (synchronous) connection
establishment and teardown functionality would fit. However, all cm events
will thereafter be handled within the library rather than being presented to the
user. Does that make sense?
Sean Hefty wrote:
as announced last week (on [email protected]), I have developed a
shared library to simplify iWARP/RDMA application development on Linux in the
course of my PhD. The library, called libiwarp, is based on libibverbs and
librdmacm - it is essentially a set of wrappers to hide some of the complexity.
I briefly toured through the code, and it seems to offer these main features:
1. Joins the rdma_cm_id and qp together into a single construct.
2. Supports synchronous rdma_cm operation.
3. Abstracts some initialization, like opening the device, creating PDs, etc.
4. Simplifies some verbs operations.
Would it be possible to submit patches against the librdmacm to integrate some
of these features?
--
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
--
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
