Really simple question for anyone here (though I suspect the NV guys can give more info than the slightly lacking doco).
What exactly is the difference between CU_CTX_SCHED_YIELD and CU_CTX_BLOCKING_SYNC?
Or more specifically, what exactly does CU_CTX_BLOCKING_SYNC do?
The general impression I get from the doco is CU_CTX_SCHED_YIELD is similar to spin, except it’s yielding in between each poll - instead of constantly polling the device as fast as possible.
But how does this differ from CU_CTX_BLOCKING_SYNC? It doesn’t seem to imply it spins or yields, almost as if it’s referring to completely different concepts - the doco almost makes it seem like spin/yield schedling, and blocking syncs refer to two different types of device polls (waiting for synchronous kernel launches / memory copies, versus waiting for streams or events).