: 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 terminate 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.

; 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.)