RE: QoS in local SA entity

["Sean Hefty" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>]

>L1. compute source address
>L2. issue kernel rdma_bind to source address and resolve <device, port,
>pkey>
>L3. issue ACM address (DGID) resolution call using (<device, port,
>pkey>, dest-ip)
>
>makes sense? if yes, what's the need in the address configuration file?

Here is where we're at today:

rdma_resolve_addr:
	- Source sends a multicast request to destination IP
	- Destination performs a path record query
	- Destination sends a response with IP to DGID mapping

rdma_resolve_route:
	- Source performs a path record query

The current implementation of ACM converts this to:
	** Source sends a multicast request to destination IP
	** Destination sends a response with IP to DGID mapping
	- Path record is constructed from multicast group information	

ACM needs to know what the local addresses are, so it can respond to requests
for those addresses.

- Sean

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html