summaryrefslogtreecommitdiff
path: root/Kernel/Module.h
diff options
context:
space:
mode:
authorAndreas Kling <awesomekling@gmail.com>2019-12-09 19:12:38 +0100
committerAndreas Kling <awesomekling@gmail.com>2019-12-09 19:12:38 +0100
commitdbb644f20cc12104a60474953c68e2bcff78b316 (patch)
tree38b745ea52f352b3ea7edacd5b10b0c9e2a45752 /Kernel/Module.h
parent7248c34e358da73d100f61df906d828f1ce97aa5 (diff)
downloadserenity-dbb644f20cc12104a60474953c68e2bcff78b316.zip
Kernel: Start implementing purgeable memory support
It's now possible to get purgeable memory by using mmap(MAP_PURGEABLE). Purgeable memory has a "volatile" flag that can be set using madvise(): - madvise(..., MADV_SET_VOLATILE) - madvise(..., MADV_SET_NONVOLATILE) When in the "volatile" state, the kernel may take away the underlying physical memory pages at any time, without notifying the owner. This gives you a guilt discount when caching very large things. :^) Setting a purgeable region to non-volatile will return whether or not the memory has been taken away by the kernel while being volatile. Basically, if madvise(..., MADV_SET_NONVOLATILE) returns 1, that means the memory was purged while volatile, and whatever was in that piece of memory needs to be reconstructed before use.
Diffstat (limited to 'Kernel/Module.h')
0 files changed, 0 insertions, 0 deletions