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

Implement a pull-through VirtualMemory Cache #65

Open
ko1N opened this issue Jul 2, 2021 · 0 comments
Open

Implement a pull-through VirtualMemory Cache #65

ko1N opened this issue Jul 2, 2021 · 0 comments
Assignees
Labels
enhancement New feature or request
Projects

Comments

@ko1N
Copy link
Member

ko1N commented Jul 2, 2021

Due to the nature of physical memory access it is sometimes inconvenient that data is paged out and inaccessible because it did not change in a while. A pull-through VirtualMemory Cache (similar to the PhysicalMemory caches) could mitigate this issue or at least reduce it a bit. Ideally the cache size is fully configurable.

It is probably best to start working on this issue after the unification of vmem/pmem.
Additionally the "user" needs to be able to access exactly which individual page lookups failed during bigger reads.

@ko1N ko1N added this to To do in Version 0.2 via automation Jul 2, 2021
@ko1N ko1N added the enhancement New feature or request label Jul 2, 2021
@ko1N ko1N self-assigned this Nov 27, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Version 0.2
  
To do
Development

No branches or pull requests

1 participant