Guy German wrote:
The problems I see with asynchronous route/arp model in the generic cm
API is that consumers will have to deal with complicated caching (that
can be implemented in the at module) and that it is not native to iwarp.
What do other people think about it ?
I don't think that they need to deal with caching. And in looking at the ib_at
code, I think that caching should be removed. A more generic SA path record
cache would work better IMO.
I would rather see an interface similar to the caching mechanisms in place for
verbs, with calls like ib_get_cached_path(), etc. In any case, I think that we
should defer adding caching in an initial implementation, and design an
appropriate SA cache separately.
- Sean
_______________________________________________
openib-general mailing list
[email protected]
http://openib.org/mailman/listinfo/openib-general
To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
