-
Notifications
You must be signed in to change notification settings - Fork 389
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
Replace AV FI_RANGE with FI_SYMMETRIC #35
Comments
FI_SYMMETRIC would be paired with FI_RANGE. For example, an app could request a range of network addresses or hostnames (host100-host200), a starting transport address (port 5000), and the number of EP per node (32). The AV would insert all hosts 100-200 into the table with ports 5000-5031 for each host. |
New AV interfaces added in 2c976eb |
bturrubiates
pushed a commit
to bturrubiates/libfabric
that referenced
this issue
Mar 4, 2015
prov/gni: explicit set av_type to FI_AV_UNSPEC
shefty
pushed a commit
that referenced
this issue
Oct 12, 2018
Pad causes wasteful alignment. The Verbs experimental XRC implementation uses some of the wasted space. Signed-off-by: Steve Welch <swelch@systemfabricworks.com>
shefty
added a commit
that referenced
this issue
Oct 12, 2018
prov/rxm: Correct pad in RXM wire protocol structure (#35)
msalnik
pushed a commit
to msalnik/libfabric
that referenced
this issue
Nov 7, 2018
Pad causes wasteful alignment. The Verbs experimental XRC implementation uses some of the wasted space. Signed-off-by: Steve Welch <swelch@systemfabricworks.com>
tstruk
pushed a commit
to tstruk/libfabric
that referenced
this issue
Oct 7, 2024
FabreX v2.8.0R10 Release
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In practice, FI_RANGE is difficult to use and harder to implement. Define an alternative method, FI_SYMMETRIC, instead, which allows an app to indicate that addresses on remote systems use the same transport addresses (port numbers), with an equal number of processes placed per node. This will simplify the implementation and the application usage of the interface, plus enable optimal storage of the data.
The text was updated successfully, but these errors were encountered: