Add non-blocking read/write transfers #68
Merged
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.
Transfer bandwidth test includes enqueueWriteBuffer and enqueueReadBuffer scenarios, both of these use blocking versions of OpenCL calls. On Intel it seems that some drivers might use CPU instead of GPU to perform the blocking transfer.
The possible solution is to add non-blocking versions of enqueueWriteBuffer and enqueueReadBuffer to the transfer bandwidth test.
As a verification, an output from running on idle machine:
and an output from running while an external app was fully utilizing the CPU:
As you can see, non-blocking transfers perform exactly the same in both runs.