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
{{ message }}
This repository has been archived by the owner on Mar 8, 2022. It is now read-only.
The "dsnvm_handle_receive_coherence" function is used to process the consistency command that the DN receives from ON in the second stage of the MRMW process, but there is no mention of local dirty page that has been modified. Is that right ?
If the page has been modified locally, direct fetch operation will overwrite the page rather than allocating a new physical page.
The text was updated successfully, but these errors were encountered:
Yeah, I looked at the function carefully, but I still didn't see the part of the operation mentioned in the paper.For example, if the xact being committed is version 1, and the dirty page in the DN is based on version 0 instead of version 1. It seems wrong to reserve the local dirty page , because the dirty page is based on the version of the old page.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The "dsnvm_handle_receive_coherence" function is used to process the consistency command that the DN receives from ON in the second stage of the MRMW process, but there is no mention of local dirty page that has been modified. Is that right ?
If the page has been modified locally, direct fetch operation will overwrite the page rather than allocating a new physical page.
The text was updated successfully, but these errors were encountered: