| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
I would like to see the opposite code for this: where we create a copy that is not attached to a data. Please point me to it. |
Sorry, something went wrong.
That's not a thing we do in TTG. What we do though is to create a data that goes out of scope before the end of the program and we detach the host copy from the data. Now the data still exists (because it is ref-counted) and has device copies but no host copy anymore. |
Sorry, something went wrong.
Signed-off-by: Joseph Schuchart <joseph.schuchart@stonybrook.edu>
We should track w2r tasks. There may be cases where an eviction is started but no pushout to the host happens afterwards before tear-down, e.g., if the data produced in a kernel is sent to another process. The tear-down will then find data in inconsistent state. Signed-off-by: Joseph Schuchart <joseph.schuchart@stonybrook.edu>
| Back | FazBrowse Home | New Git URL |
And if no readers exist on the copy.
In TTG, host-side data can disappear once its life-time ended, detaching the CPU data copy from the data. On eviction, we have no host copy to evict to so we just drop the device copy. This is not perfect as it might lead to race conditions with multiple devices but it is a step forward.