summaryrefslogtreecommitdiff
path: root/Kernel/VM/PhysicalPage.h
diff options
context:
space:
mode:
authorTom <tomut@yahoo.com>2020-09-04 21:12:25 -0600
committerAndreas Kling <kling@serenityos.org>2021-01-01 23:43:44 +0100
commitb2a52f62089e4799336cf0bf32eb307b077d2e72 (patch)
treed0e3763a1a452357c76b5fe68fa3ab1b6bc83147 /Kernel/VM/PhysicalPage.h
parente21cc4cff63c36917d83730871dfff1a9f0eb927 (diff)
downloadserenity-b2a52f62089e4799336cf0bf32eb307b077d2e72.zip
Kernel: Implement lazy committed page allocation
By designating a committed page pool we can guarantee to have physical pages available for lazy allocation in mappings. However, when forking we will overcommit. The assumption is that worst-case it's better for the fork to die due to insufficient physical memory on COW access than the parent that created the region. If a fork wants to ensure that all memory is available (trigger a commit) then it can use madvise. This also means that fork now can gracefully fail if we don't have enough physical pages available.
Diffstat (limited to 'Kernel/VM/PhysicalPage.h')
-rw-r--r--Kernel/VM/PhysicalPage.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/Kernel/VM/PhysicalPage.h b/Kernel/VM/PhysicalPage.h
index dddf89ce3b..c0cf46ac62 100644
--- a/Kernel/VM/PhysicalPage.h
+++ b/Kernel/VM/PhysicalPage.h
@@ -64,6 +64,7 @@ public:
u32 ref_count() const { return m_ref_count.load(AK::memory_order_consume); }
bool is_shared_zero_page() const;
+ bool is_lazy_committed_page() const;
private:
PhysicalPage(PhysicalAddress paddr, bool supervisor, bool may_return_to_freelist = true);