Version: 1
-Previous: f1eba85e7979486b1520f4e118c07e708986e5c8
-Head: 071454d8064f023035c5c49e82d8d4567aa13ac4
+Previous: e83c5e53d353133d843056633f43a05f32d77a6c
+Head: 0f9837af4f64eeeae8a4c168c8ccf47186c735d4
Applied:
lmc: b355854c79a1e446e87684a41663ad5aae258b73
- lid: 1c005908ee6c257f6fa290df8ce8a45e968d07ab
- refresh-temp: 071454d8064f023035c5c49e82d8d4567aa13ac4
+ lid: 0f9837af4f64eeeae8a4c168c8ccf47186c735d4
Unapplied:
acme_gid: 160551b2a4bed277f4c81b52ef33a184f43ca783
range: dfe3c8409e2e1fcc2fc11bd7f9287f1c46b36015
ibacm: add support for path lookup by LID/GID
-Support caching path data by LID/GID. We limit data
-to one path per DLID/DGID.
+Support path record lookup based on DLID or DGID. This allows
+ibacm to be used purely for path record caching, with address
+resolution being done by a user. This is needed to support
+clients that exchange LID/GID information out of band before
+connecting, or that make use of ipoib for address resolution.
Signed-off-by: Sean Hefty <sean.hefty@intel.com>
+++ /dev/null
-Bottom: 9cfb1ddbdd89bfe7a45eb80019ef27af2267dd2e
-Top: 9cfb1ddbdd89bfe7a45eb80019ef27af2267dd2e
-Author: Sean Hefty <sean.hefty@intel.com>
-Date: 2010-12-17 14:57:14 -0800
-
-Refresh of lid
-
----
-
-