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

[James Lentini]

The ability to transparently support multiple transports is key. With 
the DAT registry, consumers can use a single API to interact with IB, 
iWARP, or some other RDMA provider.

This needs to be retained.

On Wed, 13 Jul 2005, Tom Duffy wrote:

> On Wed, 2005-07-13 at 16:19 +0200, Christoph Hellwig wrote:
>> After re-evaluting things: none, just don't merged it.
>
> into gen2/trunk?
>
>> We want an RDMA layer in the kernel, and it looks like Catalin's
>> extension of the IB layer to cover iWarp aswell is the better choice,
>> in combination of taking some utility routines from kdapl and adjust
>> them to work directly ontop of that.
>
> I agree Caitlin's proposal looks good.  I appreciate concrete examples
> of how to move forward.  Let's then create a branch of trunk to start
> the merge work.
>
> What routines from kDAPL are you happy with?  What is worth keeping?
>
> -tduffy
>