Version: 1
-Previous: 69b896fd1e1a00c7e5472d298f45bbe8f992f0f9
-Head: ef3728004507256635ad95161cd92811661affbe
+Previous: 9b8004687061ffc2bbd34080f80a7eded2abaaf8
+Head: 8efbf3e8cee7854ffe423fcf120ff9302be54eac
Applied:
opt_mc_av: 1c9cb4576f95c0d2cc7bf96d33cc6efe5f6c313d
one_mc_join: ef3728004507256635ad95161cd92811661affbe
+ dyn_ah: 8efbf3e8cee7854ffe423fcf120ff9302be54eac
Unapplied:
addr_size: 8de02c47fbf595132105a7050ad6f755f49f9a7a
Hidden:
--- /dev/null
+Bottom: c93d236ca31c4be364371bb05930f374530864e6
+Top: c93d236ca31c4be364371bb05930f374530864e6
+Author: Sean Hefty <sean.hefty@intel.com>
+Date: 2011-04-01 16:03:40 -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>
+
+
+
+---
+
+