Support for runtime CPU/CUDA selection #3060
Open
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.
This PR adds support for selecting either the CPU or CUDA implementation of the dnn module at runtime. As discussed in #1852, the
#ifdef DLIB_USE_CUDA
directives intensor_tools.cpp
just need to be replaced with a runtime branch likeThe thread local variable returned by
use_cuda()
is initialized to be consistent with the current behavior. IfDLIB_USE_CUDA=True
the function,use_cuda()
will returntrue
by default.I found while making these changes that is was necessary to keep the preprocessor directives because the
cuda
namespace cannot be referenced when CUDA is not linked. Additionally, the pooling and convolution classes intensor_tools.h
have instances of both implementations as members. I couldn't find a cleaner way (with limited time) to handle those cases.