Version: 1
-Previous: 6a674fe241a658e6b858ecef9368d433f58a81f2
-Head: 8e67cb28bf3b0231f89fd6f192614e9cd327c06d
+Previous: 5d369d7f79a018216cd8ebca2741cd0f2a171177
+Head: a26b6e020fd54f16249125ed2fbf94bb93f7828e
Applied:
- dyn_ah: 2b49e6040f0fb089d17cda0859bca7759fbecf68
- refresh-temp: 8e67cb28bf3b0231f89fd6f192614e9cd327c06d
+ dyn_ah: a26b6e020fd54f16249125ed2fbf94bb93f7828e
Unapplied:
addr_size: 8de02c47fbf595132105a7050ad6f755f49f9a7a
Hidden:
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.
+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.
+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>
+++ /dev/null
-Bottom: ff1f0e0cc0c31d7a9b01b551462a6a3a0612e4b9
-Top: ff1f0e0cc0c31d7a9b01b551462a6a3a0612e4b9
-Author: Sean Hefty <sean.hefty@intel.com>
-Date: 2011-04-01 15:48:01 -0700
-
-Refresh of dyn_ah
-
----
-
-