Version: 1
-Previous: 78fc0a5dec284b122bc5e84fbceaa78f9d217548
-Head: b91dc82c3bb2ad85ef7fc3e0bb36c0e5c103df9e
+Previous: 64472c6ead62880ffa81b539608a60d3338de8b9
+Head: 6f4507038104ae5e2a16a357380d583df9cd0d59
Applied:
+ dyn_ah: 6f4507038104ae5e2a16a357380d583df9cd0d59
Unapplied:
addr_size: 8de02c47fbf595132105a7050ad6f755f49f9a7a
Hidden:
--- /dev/null
+Bottom: 4a725c3b21d37e7ff6d4e2430fc69ddf4d72920a
+Top: 4a725c3b21d37e7ff6d4e2430fc69ddf4d72920a
+Author: Sean Hefty <sean.hefty@intel.com>
+Date: 2011-04-01 14:46:34 -0700
+
+ibacm: Allocate address handles dynamically when needed
+
+ibacm allocates an address handle for every remote destination that it tracks. However, under normal operation, the handle is used infrequently - typically only once by the target service to send a response and not at all on the initiator service. Avoid the overhead of having 1 address handle per destination by allocating them dynamically only when they are needed.
+
+The exceptions to this are the address handles allocated to communicate with the SA and the primary multicast group.
+
+Signed-off-by: Sean Hefty <sean.hefty@intel.com>
+
+
+---
+
+