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
Fix device selection in PipelinedExecutor. #361
Conversation
@@ -75,6 +75,7 @@ void Executor::RunCPU() { | |||
lock.unlock(); | |||
|
|||
// Run the support ops | |||
DeviceGuard g(device_id_); |
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.
Please put it above comment, now it is misleading.
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.
Fixed.
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.
Maybe we should also put it into ``PipelinedExecutor::Build and Executor::Build
.
Signed-off-by: Michal Zientkiewicz <michalz@nvidia.com>
Added Build 591988 passed. |
Signed-off-by: Michal Zientkiewicz <michalz@nvidia.com>
CUDA device id was not properly set in executor (it always tried to run on device 0). It's been fixed with RAII DeviceGuard in all relevant functions.
Signed-off-by: Michal Zientkiewicz michalz@nvidia.com