Hello,
I am currently testing the MAGMA MIC library and have problems to understand the test cases' output. For every case, a runtime in ms is depicted. Is this the pure kernel runtime (not including host-to-device/device-to-host data transfers) or rather the total runtime, i.e., host-to-device/device-to-host data transfers + kernel runtime?
Thank you very much in advance.
Best regards
understand MAGMA output
Re: understand MAGMA output
It depends on the tester:
For BLAS routines, such as magma_zgemm, it should just be the function itself, excluding data transfers.
For _mic interface routines, such as magma_zgetrf_mic, it is also just the function itself, as the matrix A starts and ends on the MIC. There are, however, data transfers during the function that are counted.
For CPU interface routines, such as magma_zgetrf, the time includes copying the matrix to the MIC and back, as the matrix A starts and ends in CPU memory.
-mark
For BLAS routines, such as magma_zgemm, it should just be the function itself, excluding data transfers.
For _mic interface routines, such as magma_zgetrf_mic, it is also just the function itself, as the matrix A starts and ends on the MIC. There are, however, data transfers during the function that are counted.
For CPU interface routines, such as magma_zgetrf, the time includes copying the matrix to the MIC and back, as the matrix A starts and ends in CPU memory.
-mark
Re: understand MAGMA output
Thank you very much.
Do you know what is the case for the "testing_sgemv" test-case of the mic library? Is the depicted runtime referring to the function itself only, excluding data transfers?
Best regards
Do you know what is the case for the "testing_sgemv" test-case of the mic library? Is the depicted runtime referring to the function itself only, excluding data transfers?
Best regards