99
edits
Changes
Added the 4th way of accounting →Ways of accounting
== Ways of accounting ==
There are tree different approaches to user pages accounting.control:
; Account all the mappings on mmap/brk and reject as soon as the sum of VMA's lengths reaches the barrier.
: This approach is very bad as applications ''always'' map more than they really use, very often MUCH more.
; Account only the really used memory and reject as soon as {{H:title|Resident Set Size|RSS}} reaches the limit.
: This approach is not good either as the only place where pages appear in user space is page fault handler and the only way to reject is killing the task. Comparing to previous scenarion this is much worse as application won't even be able to close correctlyterminate gracefully.
; Account a part of memory on mmap/brk and reject there, and account the rest of the memory in page fault handlers without any rejects.
: This type of accounting is used in UBC.
; Account physical memory and behave like a standalone kernel - reclaim user memory when run out of it.
: This type of memory control is to be introduced later as an addition to current scheme. UBC provides all the needed statistics for this (physical memory, swap pages etc.)
== UBC user pages accounting ==
