-
Notifications
You must be signed in to change notification settings - Fork 12
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
Dirty regions detection (blocks of RAM that are been overwrite) #40
Labels
Comments
Notes :
Also, I'm thinking in a less fined grained solution that uses a map . This map, maps address to a list (or other type of container) of address ranges on buckets of 256 bytes, were each address range limited to 256 byte boundary or have a self reference to how many buckets are mapped. This idea would need more develop and tweak/profile the size of bucket, and other details |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Implement dirty regions, blocks of RAM that are been overwrite.
Probably using
std::map<Range, bool>
. Useful to optimize when is necessary to update screen texture/send TDAScreen across network, and it would necessary for DJIT CPU core.Trello card : https://trello.com/c/XmMoXWOh
The text was updated successfully, but these errors were encountered: