TBB/OpenMP device adapter need to support different launch parameters at runtime
We are seeing that some VTK-m algorithms perform significantly better when they can specify a custom task size.
We should follow the design of the CUDA DeviceAdapter to allow the user to specify backend settings like task size to use for 1D, 2D, and 3D scheduling.
Edited by Robert Maynard