Hello Sean, Thanks for replying. Still I am not able to get it completely, I have seen through the SA code please help me out in understanding SA design as a whole, my query is as follows
If some client calls cma_resolve_ib_route(), and let's assume that its local cache miss, and cma_query_ib_route() is called, this will send a SA query to the SM node CMIIW, Now on SM node I am not able to figure out that who will respond this GMP, and how requested attribute info is collected? On 4/20/07, Sean Hefty <[EMAIL PROTECTED]> wrote:
> Once SM is up on a node/switch whole network is up. Now is if some > client is trying to establish a connection with other node, client is > expected to resolve the path using sa API, I want to know how exactly > it happens in the stack? See patch 3/3 for the use of the cache. In that patch, the rdma_cm first checks to see if a suitable path record is available in the cache. If one is not found, it issues a query to the SA. The stack impact of using the cache is less than the impact of sending a path record query to the SA. > Is it possible to program local_sa_cache with some dummy path records > which resides in cache for long time? This would require changes to the current implementation.
what about this : One user command, reading path record from some file and passing this to local_sa_cache module using sysfs/ioctl, local_cache module is assuming it as a incoming path_record query and adding it to the cache. possibly some device interface is required to be added to the module if ioctl is used -Devesh
- Sean
_______________________________________________ general mailing list [email protected] http://lists.openfabrics.org/cgi-bin/mailman/listinfo/general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
