Skip to content

Conversation

@hppritcha
Copy link
Member

allow for toggling of both control/data progress models.
allow for using FI_AV_TABLE or FI_AV_MAP for av type.

@yburette

Signed-off-by: Howard Pritchard howardp@lanl.gov

@hppritcha hppritcha added this to the v2.1.0 milestone Jul 13, 2016
@yburette
Copy link
Member

@hppritcha Sounds good to me. Are these options required by the gni provider? Are there any other modifications needed to make it work?

MCA_BASE_VAR_SCOPE_READONLY,
&av_type);

return OMPI_SUCCESS;
Copy link
Member

@hjelmn hjelmn Jul 13, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hppritcha This is a good place to use the mca_base_var_enum class. You can let the variable system handle the conversion of string->int. You also get value checking for free.

@hppritcha
Copy link
Member Author

@yburette these are not required by the GNI provider but testers requested them to allow for easier triaging of potential bugs.

@yburette
Copy link
Member

@hppritcha Fair enough!

allow for toggling of both control/data progress models.
allow for using FI_AV_TABLE or FI_AV_MAP for av type.

Signed-off-by: Howard Pritchard <howardp@lanl.gov>
@hppritcha hppritcha force-pushed the topic/ofi_mtl_params branch from bbef89d to 22c8743 Compare July 28, 2016 08:35
@hppritcha
Copy link
Member Author

@hjelmn take a look now

@hppritcha hppritcha merged commit 5ff6b81 into open-mpi:master Jul 29, 2016
@hppritcha hppritcha deleted the topic/ofi_mtl_params branch May 2, 2018 02:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants