Skip to content

Conversation

@devreal
Copy link
Contributor

@devreal devreal commented Oct 18, 2024

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.

@devreal devreal requested a review from a team as a code owner October 18, 2024 20:37
@bosilca
Copy link
Contributor

bosilca commented Oct 21, 2024

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.

@devreal
Copy link
Contributor Author

devreal commented Oct 22, 2024

where we create a copy that is not attached to a data.

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.

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 <[email protected]>
@devreal
Copy link
Contributor Author

devreal commented Jan 23, 2025

This is replaced by #695

@devreal devreal closed this Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants