struct Key

Defined at line 48 of file ../../zircon/kernel/lib/page-map/include/lib/page-map/entry.h

Identifies a page in a VMO using the VMO's address in memory and the page's offset within the

VMO.

Why is it OK to use the object's address in the key? It seems unlikely we'll implement a

garbage collection or object forwarding scheme that would result in multiple entries for a

single (logically) VMO. And even if we do, it would likely manifest as an efficiency issue

rather than a correctness issue.

Required by WAVLTreeContainable.

Public Members

void * vm_object_paged_

size_t page_offset_in_vmo

std::strong_ordering operator<=> (const Key & )

Defined at line 52 of file ../../zircon/kernel/lib/page-map/include/lib/page-map/entry.h

bool operator== (const Key & )

Defined at line 53 of file ../../zircon/kernel/lib/page-map/include/lib/page-map/entry.h