I have some updates. I have noticed that for some metrics, smsp works but sm is shown as n/a. I tried with 2019.4 version.
I have uploaded 2 set of analyses.
1- For shared_load_transactions, I collected smsp__inst_executed_op_shared_ld.sum and sm__inst_executed_op_shared_ld.sum
You can download the zip report from https://gofile.io/?c=ccoHjF
2- For SP FP instructions, I collected
You can download the zip report from https://gofile.io/?c=7p58dH
I hope there are enough debug information in the report files for developers. Actually, I ran Gromacs. I have to say that such behavior may not be seen in other programs. So, it is hard to find a program from SDK for such purpose.
One more questions:
The FP operations are calculated as fadd+fmul+2*ffma. Isn’t that true?
However, in the metric table, it is written as
Can you explain that? Is that a typo?
Or the value that smsp__sass_thread_inst_executed_op_fmul_pred_on.sum gives us is actually something multiplied by 2?
Also, based on the definition of smsp, the correct number of operations (similar to nvprof) should be
4*(smsp_fadd + smsp_fmul + smsp_2*ffma).
Am I right?