>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.
I think we keep this concept. >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? I wasn't thinking about replacing existing calls, but rather adding new functions. I would start with just trying to integrate one feature, probably the simpler connection model for the active side, then look to expand from there. - Sean -- 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
