Distinguish the requested location from its target
A virtual address names a location within an address space. A physical address names the target used after translation to access system memory or other mapped resources. Depending on the architecture, device regions can also occupy physical address space. Describing virtual addresses as fake and physical addresses as real is therefore unhelpful: a virtual pointer is the legitimate address interface used by an executing program. Its interpretation depends on mappings and protection rules. This article uses an ordinary paged process as the base model. Additional translation stages in virtualization and device-specific addressing require further distinctions, rather than being silently folded into the same diagram.
Translate the same number in two spaces
With 4 KiB pages, virtual address 0x12345 splits into page 0x12 and offset 0x345. If process A maps that page to frame 0xAB and B maps it to frame 0xCD, their physical targets are 0xAB345 and 0xCD345 respectively. Numerically equal pointers can therefore refer to independent contents. Conversely, different virtual pages can map to the same frame and support sharing. Printing pointer values from two processes does not establish whether backing pages are shared. The mapping targets and sharing mode supply that information. Retain the offset through the arithmetic and identify the address-space context before interpreting either the input number or the translated result.
page_size = 4096
virtual = 0x12345
page, offset = divmod(virtual, page_size)
assert (page, offset) == (0x12, 0x345)
assert 0xAB * page_size + offset == 0xAB345
assert 0xCD * page_size + offset == 0xCD345
Virtual continuity does not require physical continuity
Consecutive virtual pages 0x12 and 0x13 can map to separated physical frames such as 0xAB and 0x50. This allows an application to use a contiguous virtual array while the operating system assembles available backing pages. A frame assignment is not necessarily permanent either; memory-management operations can change mappings while preserving the application’s address-space contract. Applications usually do not manage those details directly. Devices introduce additional constraints. A virtually contiguous buffer is not automatically an acceptable device address or a physically contiguous DMA allocation. Use the platform’s DMA interfaces rather than handing an ordinary process pointer to hardware and assuming that the address has the same meaning there.
Neither address is a free-memory counter
Reserving a large virtual region does not mean that the same amount of RAM is already occupied. Untouched regions, demand-loaded file mappings and shared pages make virtual size different from residency. A large numerical physical address is not evidence that little memory remains either: an address describes location, while capacity and usage are separate aggregates. Diagnosing memory shortage requires distinguishing reservation, commitment policy, resident pages, sharing, swap and resource limits such as container constraints. Do not infer the complete memory situation from one pointer value or one size field. State which accounting question is being answered before choosing a process or system-level metric.
Respect observation and interface limits
Most applications need their virtual addresses, not direct knowledge of physical placement. Linux interfaces such as pagemap can expose mapping-related information, but access to physical-frame numbers is restricted. Failure to obtain a number does not prove that no mapping exists. The observation also describes a particular moment, not an immutable future assignment. For performance work, begin with the evidence relevant to the problem: access order, pages touched, residency, faults and resource limits. Obtaining physical addresses is not automatically a useful diagnostic goal. Respect the supported interface and permissions, and avoid treating an observed frame number as a general-purpose capability to access or retain the underlying physical storage.