Launching smaller overlapping asynchronous kernels can have speed up if your vectors are large and you are doing reductions. This way warps stalls can be compensated for, and latencies can be hidden. Not sure what you mean "the way it currently is" though... On Tue, Apr 24, 2012 at 2:21 PM, Jed Brown <[email protected]> wrote:
On Tue, Apr 24, 2012 at 14:12, Daniel Lowell <[email protected]> wrote:
I'm writing a vector type with uses flag synching like you have in PETSc with Vec CUSP, however it uses asynchronous kernel launches (pipeling,etc..) and autotuned kernels. Not quite ready for primetime, but we have seen the value of it in terms of speed up.
Okay, but why do dozens of small kernel launches when all the data is available up-front? I'm just skeptical that VecMDot should be implemented for CUDA the way it currently is.
-- Daniel Lowell