Separating latency report for read and write requests

[bigplanewangyue]

How can I distinguish the task time for read and write operations in averagetimetracer.go? And in metrics.cvs , req_average_latency seems to be the average of all the latencies for a specific location？

[JunjoFor]

If you print memory traces with -trace-mem you can get the time each memory task started and ended so you can calculate the latencies you want.

[syifan]

The solution should be creating two different tracers with different trace filters. See here for the filter. https://github.com/sarchlab/mgpusim/blob/v3/samples/runner/report.go#L180. You can try to print the task and see what information is available in the filter. But I think the What field should be able to separate the read and write requests.

I have also updated the related parts in the Akita book. https://www.notion.so/syifan/2-4-Hooking-and-Tracing-Ongoing-0b947051beb74868a2a74de81bafe40c?pvs=4#12919baeaf86804ea2c3c1da13af059d. I hope it is helpful.

[bigplanewangyue]

when i print the what and where field , i found they are null？

[syifan]

Are you printing the task in the EndTask function. The task passed to the EndTask only contains the task ID and end time. You may need to match it with the original task to identify the where field.