[openib-general] kDAPL: ready for gen2/trunk/ inclusion?

[James Lentini]

The benefit is that all RDMA related events are produced by the same 
source.

Contrasting this with the OpenIB API may useful. In the OpenIB 
API, events are delivered via both CQ work completions and callbacks.

If you look through the DAPL event subsystem, you'll see that it does 
take a bit of code to implement this feature. Duplicating this 
functionality in each consumer wouldn't be efficient. Consumers would 
be better off handling the work completions and callbacks directly.

james

On Wed, 13 Jul 2005, Sean Hefty wrote:

>> In addition to the streamlined connection management interface, kDAPL
>> also provides a unified event model. This is another feature that the
>> verbs do not provide.
>
> Can someone educate me on the benefits of a "unified event model" and why a
> consumer couldn't easily perform the same functionality?