Working on my own project,
I was wondering… Would it make any sense to code the occupancy estimation formula from the XLS to search for the best block sizes at runtime, before running my kernel ?
I’m currently using the occupancy calculator, but this question just popped out.
Major problem for that is, that you need your register usage as an input, which you usually only get at compile time, but you would probably want it as a constant in your code. Now, one could put it in some resource file generated during the build process and read at runtime, but that’s kind of ugly. Is there any way to get the register requirements of a kernel at runtime?