-
Notifications
You must be signed in to change notification settings - Fork 423
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
TOOLS/PERF: Enable specifying different memory types for sender and receiver #4607
TOOLS/PERF: Enable specifying different memory types for sender and receiver #4607
Conversation
…eceiver in perftest
Can one of the admins verify this patch? |
Example:
|
ok to test |
Mellanox CI: FAILED on 3 of 25 workers (click for details)Note: the logs will be deleted after 30-Dec-2019
|
Mellanox CI: FAILED on 4 of 25 workers (click for details)Note: the logs will be deleted after 30-Dec-2019
|
@dmitrygx I reworked the memory type parsing a little bit so that memory types added in the future will be automatically supported. Also switched to |
Mellanox CI: FAILED on 7 of 25 workers (click for details)Note: the logs will be deleted after 30-Dec-2019
|
the failures are relevant:
|
Mellanox CI: FAILED on 2 of 25 workers (click for details)Note: the logs will be deleted after 09-Jan-2020
|
Mellanox CI: PASSED on 25 workers (click for details)Note: the logs will be deleted after 09-Jan-2020
|
bot:pipe:retest |
@souravzzz the failure is unrelated to your PR |
bot:pipe:retest |
@alinask, plz review as well |
Mellanox CI: PASSED on 25 workers (click for details)Note: the logs will be deleted after 14-Jan-2020
|
What
Add support for specifying different memory types as source and destination in perftest
Why ?
Currently the same memory type is used by the sender and the receiver.
Hence, only H-H and D-D transfers can be tested.
This PR adds support for H-D and D-H transfers.
Backward compatibility is preserved by using the same memory type as source and destination if only one is specified.