sync #29
Merged
sync #29
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If a listener is destroyed while it has a pending connect request which has not been dispatched yet, we must release it. Otherwise, rdma_destroy_id() will hang while waiting for all events to be released.
- added keepalive_interval value to uct_iface_params structure
UCP: implement ucp_tag_msg_recv_nb as ucp_tag_msg_recv_nbx. UCP: copy user data only if flag is present. DOC: updated news.
UCT/IB: get roce ndev name according to right gid but not fixed gid 0
- Destroy all connections to flush requests before destroying memory pools - Avoid removing elements from connections map while iterating over it
JENKINS: update cuda module version to 11.1.1
- suppressed incorrect assert on keepalive remove ep - renamed flag UCP_EP_FLAG_TEMPORARY to UCP_EP_FLAG_INTERNAL - mem-type EP's are marked by UCP_EP_FLAG_INTERNAL flag - fixed ep-destroy flow for memtype EPs
…rr_cb UCP/WIREUP/GTEST: Fix dead code in CM disconnect
- there was possible double free of string when user tried to set incorrect value using ucs_config_parser_set_value function - added gtest
AZP: add warning for azure
Fixes for iodemo and listener destroy flow
…-conf-value UCS/CONFIG: fixed crash on incorrect value set
…daemon-server-loop TOOLS/VFS: Implement mount daemon server loop
…and-expose UCS/VFS: Connect to daemon and expose dummy filesystem
UCP/CORE: Remove unused pending queue
In order to catch cuda memory events even when Cuda is statically linked, use bistro.
JENKINS: test CM's fallback in client-server testing
Make memory hooks work with static libcudart, by using bistro hooks for cuda driver API
UCP/WORKER: Fix mis-spelling
UCT/IB/MLX5: DV UAR alloc type NC support
…-req UCP/EP: set callback on close request.
Allows passing Cuda -L<path> flag to static build example, without passing -lcudart.
JUCX: add request status field.
test_sockaddr.cc - NEGATIVE_RETURNS - "index" is passed to a parameter
that cannot be negative. [Note: The source code implementation of the
function has been overridden by a builtin model.]
uct_cm.c - PRINTF_ARGS - Argument "self->iface" to format specifier "%p"
was expected to have pointer type but has type "struct uct_base_iface".
ucp_hello_world.c - USE_AFTER_FREE - Dereferencing freed pointer "msg"
wireup_cm.c - USE_AFTER_FREE - Passing freed pointer "conn_request" as
an argument to "ucs_log_dispatch" ("uct_listener_reject" frees
"conn_request".).
UCP/WIREUP: Allow EP check during WIREUP phase
…rt-static-is CUDA/TEST: Check if libcudart_static is present for memory hook test
UCP/UCT/TEST/EXAMPLES: Fix several coverity issues.
Get device/vendor ids of SF from its parent PCI
UCS/DATASTRUCT: Add allow_list data struct
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What
Describe what this PR is doing.
Why ?
Justification for the PR. If there is existing issue/bug please reference. For
bug fixes why and what can be merged in a single item.
How ?
It is optional but for complex PRs please provide information about the design,
architecture, approach, etc.