Version: 1
-Previous: 98d14ae4e95ab32268aab0914c4a061a2b69651e
-Head: ac48063bfb7750cba235349c806cbd8cd61ea3e6
+Previous: cc3a8d5160840cb581044ce0927c1994b360b14b
+Head: 5c356d7d1da9016835e25099becd7224970314b5
Applied:
- xref-lid: cc77279d508eb463c843ab4d0b4fcd5e26a7c549
- refresh-temp: ac48063bfb7750cba235349c806cbd8cd61ea3e6
+ xref-lid: 5c356d7d1da9016835e25099becd7224970314b5
Unapplied:
ibacm-check-for-nodelay-on-pat: 1540687d721504ec1810aac7cc53ec7272415eb9
Hidden:
+++ /dev/null
-Bottom: 1fcbb0d2b361b8a2ed7ce1d4252ecc8c4be8ae71
-Top: 1fcbb0d2b361b8a2ed7ce1d4252ecc8c4be8ae71
-Author: Sean Hefty <sean.hefty@intel.com>
-Date: 2010-12-13 15:38:02 -0800
-
-Refresh of xref-lid
-
----
-
-
Author: Sean Hefty <sean.hefty@intel.com>
Date: 2010-12-13 10:35:40 -0800
-ibacm: store endpoint data based on GID/LID
+ibacm: cross-reference destination endpoints in LID map
+
+After resolving remote endpoint information, we record
+the destination data in a specific dest_map based on the
+destination's type. To support queries against cached
+data that uses alternate address information, such as
+LID or GID, also reference the destination in the LID
+dest_map. This allows us to find the destination based
+on LID, as well as the original address.
Signed-off-by: Sean Hefty <sean.hefty@intel.com>