Clean up reachable framework / components #4225
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bwbarrett
force-pushed
the
reachable
branch
from
a38cf06 to
f6fc407
Compare
bwbarrett
force-pushed
the
reachable
branch
from
f6fc407 to
7a2790a
Compare
jsquyres
requested changes
Sep 19, 2017
There was a problem hiding this comment.
Pretty minor nits, and some compiler warnings:
base/reachable_base_alloc.c:32: warning: no previous prototype for ‘opal_reachable_allocate’
base/reachable_base_alloc.c: In function ‘opal_reachable_allocate’:
base/reachable_base_alloc.c:53: warning: assignment from incompatible pointer type
opal/test/reachable/Makefile
Outdated
| CFLAGS = -g | ||
| CXX = ortec++ | ||
| CXXFLAGS = -g | ||
| FFLAGS = -g |
There was a problem hiding this comment.
Nit: are FFLAGS and CXXFLAGS necessary
opal/test/reachable/Makefile
Outdated
|
|
||
| clean: | ||
| rm -f $(PROGS) *~ | ||
|
|
There was a problem hiding this comment.
Nit: blank line at end of file.
| CQ_NO_CONNECTION = 0, | ||
| CQ_DIFFERENT_NETWORK = 50, | ||
| CQ_SAME_NETWORK = 100 | ||
| }; |
There was a problem hiding this comment.
You define the same values in reachable_weighted.c (and also the TCP BTL). Should these be put in reachable.h and prefixed with OPAL_REACHABILITY_ or somesuch?
There was a problem hiding this comment.
I thought about it, but I don't actually want them to be part of the public interface; it means we can't tweak the algorithms and have to live with those choices going forward. Imagine a netlink version that counted router hops as part of the weight. Or ping latency, or something like that. Those would be hard if we baked the constants into the API.
If you look at the usNIC BTL (which is where we should be moving the TCP BTL), there's no need for these constants, because it's the relative weights that matter. So in time, we'll be removing them from the TCP BTL.
bwbarrett
force-pushed
the
reachable
branch
from
7a2790a to
6e2fe50
Compare
Add a check for link-local IPv6 addresses to the net interface to support better computation of network pairings in the weighted reachable component. Signed-off-by: Brian Barrett <bbarrett@amazon.com>
Ralph and Jeff created the reachable framework and added the netlink component based on code copied from the usnic btl. However, they never renamed all the symbols from the libnl compatibility code. This patch finishes the rename. Signed-off-by: Brian Barrett <bbarrett@amazon.com>
Initialize the reachable framework during opal_init() and tear it back down during opal_finalize(). The framework was never used, so the lack of initialization didn't matter, but this is a required step in using the framework. Signed-off-by: Brian Barrett <bbarrett@amazon.com>
Based on work from usNIC, the best way to use the reachability information the reachable components return is to build a connectivity graph between the two peers and run a bipartite graph solver. Rather than returning the "best" pairing, the reachability framework now returns the entire mapping, allowing a (soon to be added) graph solver to build the "optimal" connectivity pairing. Practically, this means changing the return type of the reachable() function and rewriting the weighted_reachable() function to return the full mapping. The netlink_reachable() function still always returns NULL. At the same time, fix bit-rot in the weighted component and enable builds of the component by removing the opal_ignore. Also, add IPv6 support to the weighted component to support both use cases in the TCP BTL. Signed-off-by: Brian Barrett <bbarrett@amazon.com>
The netlink reachable component has never been released in a usable form, but had code copied from usNIC to support both libnl-1 and libnl-3. If nothing else, this code was a little buggy in handling the case where libnl-3 but not libnl-route-3 were installed. Jeff and I decided to drop libnl-1 support from the netlink reachable component, given that it's getting pretty old and the weighted component provides the same information that the TCP BTL and OOB are using today, so libnl-1 customers won't see a step backwards from where they are today. Signed-off-by: Brian Barrett <bbarrett@mazon.com>
The netlink component's libnl wrapper code returned the next hop in the route table to allow the calling code to differentiate between same and different networks, which is a fine comparison for IPv4, but is pretty expensive for IPv6 (coming soon to a netlink component near you). Rather than provide extra information (the address of the next hop), just provide whether there is a gateway or not, which is all the netlink component actually needs. Signed-off-by: Brian Barrett <bbarrett@amazon.com>
Add IPv6 support to the netlink component's utility wrappers around libnl-3. Signed-off-by: Brian Barrett <bbarrett@amazon.com>
Wire up the libnl utilities Jeff and Ralph added previously to the netlink reachable component so that it actually does work. The algorithm is a bit simplistic, but should work for our use cases. If there's a route, assume the two interfaces can talk. If there's no gateway, assume the two interfaces are in the same subnet, and give preference to that connection. If there's a gateway, assume there's a route, but the interfaces are not in the same subnet. Signed-off-by: Brian Barrett <bbarrett@amazon.com>
Amazon is going to use the reachable framework to fix some connection bugs in the TCP BTL, so claim support ownership of the weighted and netlink components. Signed-off-by: Brian Barrett <bbarrett@amazon.com>
Add test suite for netlink and weighted reachable components. We don't have a great way of running components through unit tests today, so make them stand-alone tests that are run with mpirun and such. Signed-off-by: Brian Barrett <bbarrett@amazon.com>
bwbarrett
force-pushed
the
reachable
branch
from
6e2fe50 to
48f8236
Compare
|
we really need to get warnings to the point where "make > /dev/null" pops the new warnings easily... Anyway, comments fixed. |
jsquyres
approved these changes
Sep 19, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The reachable framework was largely some code copied from usNIC by Jeff and Ralph, but never got finished. This patch series makes the reachable framework usable, at least for the purposes of the TCP BTL.
After lots of discussion with Jeff, it became clear that the primary use for the reachable framework should be as input to the bipartite graph code also recently moved from usNIC to util/, so the interface for the framework has been tweaked slightly to better match the inputs of the graph solver.