Skip to content
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

UCT/API: New api to use mem flags and distance in perf estimate #10546

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

brminich
Copy link
Contributor

What?

Define API to pass memory flags to perf estimation function

Why?

part of #10540

UCT_PERF_ATTR_FIELD_REMOTE_MEMORY_FLAGS = UCS_BIT(6),

/** Enable @ref uct_perf_attr_t::distance */
UCT_PERF_ATTR_FIELD_DISTANCE = UCS_BIT(7),
Copy link
Contributor

Choose a reason for hiding this comment

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

alignment

@@ -1068,7 +1103,7 @@ ucs_status_t uct_ep_query(uct_ep_h ep, uct_ep_attr_t *ep_attr);
* @return Nonzero if reachable, 0 if not.
*/
int uct_iface_is_reachable_v2(uct_iface_h iface,
const uct_iface_is_reachable_params_t *params);
uct_iface_is_reachable_params_t *params);
Copy link
Contributor

Choose a reason for hiding this comment

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

We need to add unit tests to gtest\uct to test the API. Currently we don't have such tests at all. We only cover this API in gtest\ucp\test_ucp_wireup.cc, gtest\uct\ib\test_ib_pkey.cc. However, this is not enough. We need to test the exact API using different input parameters. I think adding a simple one at least for new fields would be good way to start.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants