On Tue, 23 Aug 2005, Roland Dreier wrote:
> The listen side is even simpler:
>
> rdma_listen():
> inputs: local service, event callback, consumer context
>
> Wait for connection requests and pass events to the consumer's
> callback. I'm not sure if/home we want to support binding to
> a particular IP address. The current IB CM in Linux doesn't
> support binding a listen to a single device or port, and even
> if it did it's not clear how to handle binding to one IP
> address when a port has more than one IP.
>
> I guess the event callback would receive a device pointer and
> the same RDMA transport address union I talked about above
> when discussing address resolution.
>
> It would be possible to have another function like
> rdma_getpeername() that takes the transport address and
> returns a source IP address.
To be complete, the API needs an rdma_getpeername() function:
rdma_getpeername():
inputs: connected QP
outputs: peer IP address
> In the IB case this would do an
> ATS reverse lookup. However, I hate this idea. iSER already
> uses the CM private data to pass the source IP in the IB case,
> and I would much rather fix NFS/RDMA to do the same thing (so
> we can just kill ATS as an address resolution method).
_______________________________________________
openib-general mailing list
[email protected]
http://openib.org/mailman/listinfo/openib-general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
