Use same kernel launcher infrastructure for threading and GPUs

BarryFSmith avatarBarryFSmith created an issue

There is a great deal of commonality (and a few differences) between the code used for launching kernels with pthreads, openmp, cusp/cuda and opencl. It would be good if all the kernel launching code could be unified across these instead of having different code for cusp/cuda and opencl and the threading.

At the same time setting up a unified system to manage kernel fusion would be fantastic.

Allowing different parts of the vector to be handled by CPU and GPU kernels would be nice. It is stilly to use only one of the two compute engines to perform operations.

Comments (1)

  1. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.