diff options
author | Andreas Kling <awesomekling@gmail.com> | 2019-12-09 19:12:38 +0100 |
---|---|---|
committer | Andreas Kling <awesomekling@gmail.com> | 2019-12-09 19:12:38 +0100 |
commit | dbb644f20cc12104a60474953c68e2bcff78b316 (patch) | |
tree | 38b745ea52f352b3ea7edacd5b10b0c9e2a45752 /Kernel/Syscall.h | |
parent | 7248c34e358da73d100f61df906d828f1ce97aa5 (diff) | |
download | serenity-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/Syscall.h')
-rw-r--r-- | Kernel/Syscall.h | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/Kernel/Syscall.h b/Kernel/Syscall.h index aa70ab1699..a7db981c4c 100644 --- a/Kernel/Syscall.h +++ b/Kernel/Syscall.h @@ -144,7 +144,9 @@ typedef u32 socklen_t; __ENUMERATE_SYSCALL(module_unload) \ __ENUMERATE_SYSCALL(detach_thread) \ __ENUMERATE_SYSCALL(set_thread_name) \ - __ENUMERATE_SYSCALL(get_thread_name) + __ENUMERATE_SYSCALL(get_thread_name) \ + __ENUMERATE_SYSCALL(madvise) \ + __ENUMERATE_SYSCALL(purge) namespace Syscall { |