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/CUDA_IPC: Increase MAX_PEERS and MAX_STREAMS #10258

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

Akshay-Venkatesh
Copy link
Contributor

Why ?

Need this ensure greater concurrency for a larger count of peers reachable by cuda_ipc.

@@ -30,7 +30,7 @@ static ucs_config_field_t uct_cuda_ipc_iface_config_table[] = {
"Max number of event completions to pick during cuda events polling",
ucs_offsetof(uct_cuda_ipc_iface_config_t, max_poll), UCS_CONFIG_TYPE_UINT},

{"MAX_STREAMS", "16",
{"MAX_STREAMS", "128",
Copy link
Contributor

Choose a reason for hiding this comment

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

can we use UCS_PP_MAKE_STRING(UCT_CUDA_IPC_MAX_PEERS) here?
what happens if the user sets MAX_STREAMS config to a value larger than UCT_CUDA_IPC_MAX_PEERS?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Having larger MAX_STREAMS than UCT_CUDA_IPC_MAX_PEERS allows cuda-ipc transport to round-robin select among more number of streams. It wouldn't be a functional or performance issue in my opinion although it is unlikely to improve performance.

Copy link
Contributor

@yosefe yosefe left a comment

Choose a reason for hiding this comment

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

What happens if a user sets the value of MAX_STREAMS to >128?
Seems it's not documented and not checked that the config value does not exceed the array size

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