You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've done the same thing specifying device({0,1,2}) instead of device(3) and I see a similar pattern: data is always transferred between device number 0 and device(x).
So it seems the openmp runtime is handing 0 as the device number in the ompt_callback_target_data_op_emi callback both for the initial device num (the number of devices, according to the openmp spec), and the true device number 0.
A perhaps separate issue is that, (at least) for Record DataOp records, src_addr==dest_addr==(non-initial device number).
The text was updated successfully, but these errors were encountered:
I added the following to this repo's OMPT example:
The corresponding output I see is:
I've done the same thing specifying device({
0
,1
,2
}) instead of device(3
) and I see a similar pattern: data is always transferred between device number 0 and device(x
).So it seems the openmp runtime is handing 0 as the device number in the
ompt_callback_target_data_op_emi
callback both for the initial device num (the number of devices, according to the openmp spec), and the true device number 0.A perhaps separate issue is that, (at least) for Record DataOp records,
src_addr==dest_addr==(non-initial device number)
.The text was updated successfully, but these errors were encountered: