-
Notifications
You must be signed in to change notification settings - Fork 428
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
base: master
Are you sure you want to change the base?
UCT/CUDA_IPC: Increase MAX_PEERS and MAX_STREAMS #10258
Conversation
@@ -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", |
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 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?
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.
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.
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.
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
Why ?
Need this ensure greater concurrency for a larger count of peers reachable by cuda_ipc.