-
Notifications
You must be signed in to change notification settings - Fork 495
UCT/IB/ROCE: Use ipv6 non link-local GID in priority #10939
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
src/uct/ib/base/ib_device.c
Outdated
| {UCT_IB_DEVICE_ROCE_V1, AF_INET6} | ||
| struct { | ||
| uct_ib_roce_version_info_t info; | ||
| int skip_ll; /* link-local not allowed when true */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- maybe inverse to simplify - "allow_ll" or "is_ll"
- i'd explicitly initialize this value to 0 when applicable (line 1086, 1088 etc)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
| } | ||
|
|
||
| static int uct_ib_gid_is_ipv6_ll(const union ibv_gid *gid) | ||
| { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can reuse IN6_IS_ADDR_LINKLOCAL?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fixed
What?
When selecting RoCE GID, search for IPv6 non link-local before trying to use IPv6 link-local GID.
Why?
Some clusters only have
gid_index=3usable. Manually settingUCX_IB_GID_INDEX=3is cumbersome and error-prone.How?
Relevant cli:
show_gids. Tested on two clusters: