Caitlin Bestler wrote:
The wr_id field is the "minimal support" that I was referring to (that and the context on callbacks).DAPL and IT-API really need more than that to optimally implement features such as: storing the ULP's 64-bit cookie. controlling "notification status" on a per-DTO level rather than just always leaving the CQ on a "next event" basis. implementing graceful disconnect (disconnect after the last send request completes). allowing the ULP to flush a request through as a marker. returning the EP or RMR pointer with the completion. The 64 bit wr_id is fully consumed just implementing the first option. Without further support the Access Layer (DAT/IT-API/whatever) must create its own parallel data structure to shadow the work request (a DTO_COOKIE in the reference implementation).
The assumption being made here is that there needs to be another abstraction layer on top of the existing core layer. I don't think that an optimal implementation would want this.
- Sean _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
