Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The transition from exclusive state to shared state must be accompanied by copying of actual state values. #57

Open
IvanPopov opened this issue Dec 16, 2021 · 1 comment

Comments

@IvanPopov
Copy link

m_spExclusiveState[0].IsMostRecentlyExclusiveState = false;

Most of the time, resources are exclusive and they make the transition on first use to another queue, tipically during PostSubmitUpdateState() -> SetSharedResourceState(). Does I undertand right that we have to copy actual exclusive state to shared in order to be sure that next transition as shared resource will be with correct state "before" ?

@jenatali
Copy link
Member

Shared resource states are only used on resources that are "simultaneous access." For these resources, states "decay" to COMMON at the end of every ExecuteCommandLists group. A shared state means that no barriers have actually been issued, but the resource has been read from in a "promotable" way. So, no, I don't think anything is missing here.

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

No branches or pull requests

2 participants