[ofa-general] Re: [PATCH RFC] RDMA/CMA: Allocate PS_TCP ports from the host TCP port space.

[Sean Hefty]

> In the RFC patch I posted, the socket is _just_ to allow binding to a 
> port/addr.  Its not used for anything else.  From the native stack's 
> perspective, its a TCP socket in the CLOSED state (but bound) I guess.

For RDMA, I think we're somewhere in between binding to an address, 
versus mapping the address.  We map the address to an RDMA device, but 
also use that address in connections.  So, we do a little more than 
simply map the address to a device, but if the address migrates to 
another device, we don't follow it.

I can't really think of any issues that might be caused by this, but I'm 
not sure.  If an app is listening on an address the goes away, would a 
new wildcard listen work?

> By active, do you mean in the ESTABLISHED state?

Yes

> What do you mean by changing the API? Adding a new port space enum?

I was thinking of replacing the rdma_cm port space enum with something 
like IPPROTO_TCP, but doing that probably doesn't matter.

- Sean